This website requires JavaScript.
Explore
Help
Sign In
ExternalVendorCode
/
openwrt
Watch
1
Star
0
Fork
0
You've already forked openwrt
mirror of
https://github.com/openwrt/openwrt.git
synced
2024-12-23 15:32:33 +00:00
Code
Issues
Actions
7
Packages
Projects
Releases
Wiki
Activity
5106f554bb
openwrt
/
package
/
libs
/
openssl
/
files
/
padlock.cnf
4 lines
41 B
Plaintext
Raw
Normal View
History
Unescape
Escape
openssl: add legacy provider This adapts the engine build infrastructure to allow building providers, and packages the legacy provider. Providers are the successors of engines, which have been deprecated. The legacy provider supplies OpenSSL implementations of algorithms that have been deemed legacy, including DES, IDEA, MDC2, SEED, and Whirlpool. Even though these algorithms are implemented in a separate package, their removal makes the regular library smaller by 3%, so the build options will remain to allow lean custom builds. Their defaults will change to 'y' if not bulding for a small flash, so that the regular legacy package will contain a complete set of algorithms. The engine build and configuration structure was changed to accomodate providers, and adapt to the new style of openssl.cnf in version 3.0. There is not a clean upgrade path for the /etc/ssl/openssl.cnf file, installed by the openssl-conf package. It is recommended to rename or remove the old config file when flashing an image with the updated openssl-conf package, then apply the changes manually. An old openssl.cnf file will silently work, but new engine or provider packages will not be enabled. Any remaining engine config files under /etc/ssl/engines.cnf.d can be removed. On the build side, the include file used by engine packages was renamed to openssl-module.mk, so the engine packages in other feeds need to adapt. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
2023-03-10 20:53:25 +00:00
[padlock_sect]
openssl: config engines in /etc/ssl/engines.cnf.d This changes the configuration of engines from the global openssl.cnf to files in the /etc/ssl/engines.cnf.d directory. The engines.cnf file has the list of enabled engines, while each engine has its own configuration file installed under /etc/ssl/engines.cnf.d. Patches were refreshed with --zero-commit. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
2022-02-21 00:09:28 +00:00
default_algorithms = ALL
Reference in New Issue
Copy Permalink