Bill,
I agree that it's usually better to let the SSL implementation pick
the ciphers.
I have a certain device that I'd like to talk to that is running on an
underpowered embedded CPU. When I let OpenSSL pick the ciphers, it
chooses something like EDH-RSA-AES-SHA and takes about 3.5 seconds to
Bill,
For now, using pyOpenSSL is acceptable. I just discovered that the
web.py framework wants pyOpenSSL. Since my project is also using
web.py, I'll need pyOpenSSL anyway.
Thank you,
--Chris
On Thu, Sep 10, 2009 at 1:14 PM, Bill Janssen wrote:
> Chris,
>
> OK, seems reasonable. Thanks. In
Bill Janssen wrote:
> OK, seems reasonable. Thanks. In the near term, can you do this with
> M2Crypto or PyOpenSSL?
>
> When I started this update in 2007, we were trying to keep the API
> simple to avoid confusing people and avoid competition with the two
> full-fledged toolkits out there. But
Chris,
OK, seems reasonable. Thanks. In the near term, can you do this with
M2Crypto or PyOpenSSL?
When I started this update in 2007, we were trying to keep the API
simple to avoid confusing people and avoid competition with the two
full-fledged toolkits out there. But I don't see any real re
Thanks, Chris. Can you explain why you want to set the cipher list
explicitly? IMO, it's usually better to select a security scheme (TLS1,
or SSLv3, etc.), and let the implementation pick the cipher list.
Bill
Chris Frantz wrote:
> Done.
>
> Attached to Issue 3597, which is a similar request
Done.
Attached to Issue 3597, which is a similar request to mine.
Best Regards,
--Chris
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/
Hello Chris,
Can you post your patch to the Python bug tracker please -
http://bugs.python.org
Patches posted to this list tend to get lost...
Thanks
Michael
Chris Frantz wrote:
Greetings,
I would like to be able to set the cipher list when creating an SSL
connection. It appears that the
