https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217703
--- Comment #14 from Melvyn Sopacua <m.r.sopa...@gmail.com> --- Update, for reference: This is an issue in Python upstream. Python uses #ifdef OPENSSL_NPN_NEGOTIATED to detect support. This is always defined in the OpenSSL 1.1 header (as opposed to OpenSSL 1.0.2 and earlier) and the symbols are guarded by #ifndef OPENSSL_NO_NEXTPROTONEG. The combo yields Python enabling support, but it not being available. This has been wrong from Python since the beginning, since the first commit introducing NPN already defined OPENSSL_NO_NEXTPROTONEG [1], but they've been able to get away with it till now. Of course, a variable saying something is not disabled, is a braindead concept in OpenSSL general source, as you can't detect if it's disabled if it is not born yet (in earlier versions). Working on a patch for upstream. @koobs I assume separate report if I'd like that patch included in the ports tree? [1] https://github.com/openssl/openssl/commit/68b33cc5c7aa1bb98e95bfb4b61c34192a7a50e3 -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
