Configurable loading of OpenSSL providers
@bukka arbeitet bereits daran.
Seit 06.10.2023.
- Vorherrschende Sprache
- C
- Sterne
- 40.4k
- Forks
- 8.1k
- Ø Merge
- 2 T. 13 Std.
- Gemergte PRs (30 T.)
- 96
Beschreibung
Description
Since OpenSSL 3, some ciphers are not available unless users configure some openssl.cnf file. This is not always possible on certain hosting configurations, so allowing this would unbreak applications depending on this feature.
Today, Windows .p12 files are still being generated using legacy ciphers, so PHP applications relying on this feature are not working out of the box. Distros are dropping OpenSSL 1.x.x since upstream support ended, current apps are struggling with this.
An example of legacy support added to a libssl-dependent app for guidance:
https://github.com/mtrojnar/osslsigncode/pull/194
If legacy provider is not planned to be enabled by default, please consider allowing to enable this programmatically at least. Thank you.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.