>> Also, for Python 2.5 and earlier, any SSL-based code is vulnerable to a MitM >> anyway, so this can only be an issue for code using the new APIs in Python >> 2.6. > > That's not going to stop the > wannabe-self-proclaimed-so-called-vulnerability-"experts" from whining > about Python not releasing updated binary distributions though. :-( The Windows binaries currently build with 0.9.8g. Since changing that would be a source code change (even though just a single line), I think a full source release would be necessary (most likely then for both 2.6 and 3.1). Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4