Date: Sat, 10 Jun 2017 14:23:02 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 217703] lang/python36: Remove BROKEN_SSL for openssl-devel Message-ID: <bug-217703-21822-GTGztChBxF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217703-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-217703-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217703 --- Comment #14 from Melvyn Sopacua <m.r.sopacua@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 be= en able to get away with it till now. Of course, a variable saying something is not disabled, is a braindead conc= ept 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/68b33cc5c7aa1bb98e95bfb4b61c34192= a7a50e3 --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217703-21822-GTGztChBxF>