[Python-Dev] openSSL and windows binaries (original) (raw)

"Martin v. Löwis" martin at v.loewis.de
Wed Aug 9 09:16:19 CEST 2006

Gregory P. Smith schrieb:

disabling/enabling a cipher in openssl that isn't commonly used and isn't even directly exposed via any API to a python user hardly sounds like dropping a feature to me.

Strictly speaking, it is dropping a feature: a connection that can get established with 2.5b3 might not get established with 2.5c1, assuming a server that requires some IDEA-based cipher.

(any sane SSL connection will negotiate AES or 3DES as its cipher; IDEA isn't required)

Ok, I'll believe you that there isn't a practical risk associated with dropping that algorithm; I'll see what I can do.

If the release manager declares, "absolutely no changes to the windows build process!"

He didn't declare that: bug fixes are always possible. He declared "absolutely no new features without explicit permission".

Then clearly none of the changes I submitted will make it in and neither would removing any hint of IDEA in 2.5 as they're both too late.

Those changes still need permission, as they constitute a new feature.

yeah i'd just do that if you're worried about the code being in the binary causing a problem.

See, my own worries come from the "if". Should I risk breaking somebody's application just because somebody else is worried about breaking patents? You haven't indicated whether you also worry: do you?

Regards, Martin

More information about the Python-Dev mailing list