https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273656
John W. O'Brien <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #6 from John W. O'Brien <[email protected]> --- Apologies to those who might have seen a variation on this note elsewhere already. The good news is that security/py-cryptography since 45.0.0 (45.0.7 as of 2025-11-11 via [0]) has handled inability to load the OpenSSL legacy provider as a warning instead of a failure (see also [1]). The bad news is that if the emission of the warning is disruptive to you, you are expected to find a way to set the CRYPTOGRAPHY_OPENSSL_NO_LEGACY environment variable. As an alternative, I have proposed to disable loading the legacy provider in bug #299419. [0] https://cgit.freebsd.org/ports/commit/security/py-cryptography?id=505f42c58af1c1e55abc25f6f2f3166ac960685a [1] https://github.com/pyca/cryptography/commit/ddc364d28b480010f527c9838906992a27d4b55a -- You are receiving this mail because: You are the assignee for the bug.
