full-disclosure - Re: Python ssl handling could be better...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTi=qonSyrpZgQyOcnxRc=rTxuPADkqNbjpKY193O@mail.gmail.com>
Date: Sat, 5 Mar 2011 14:35:57 +1100
From: dave b <db.pub.mail@...il.com>
To: Marsh Ray <marsh@...endedsubset.com>
Cc: full-disclosure <Full-Disclosure@...ts.grok.org.uk>
Subject: Re: Python ssl handling could be better...

Marsh, the thing is that the ssl module was only introduced in python 2.6. [0]
There has been other options for a _long_ time. As an example, (for
https traffic) pycurl. So python developers can and do use public wifi
without problems. Only the ones who do not read warning messages are
at risk.  Of course a fair amount of code would have been written
before the warnings were added...

[0] http://docs.python.org/whatsnew/2.6.html#improved-ssl-support

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/