[Twisted-Python] Twisted+M2Crypto patch

Eugene Coetzee projects at reedflute.com
Wed Aug 11 19:04:14 EDT 2004


J C Lawrence wrote:

>On Wed, 11 Aug 2004 17:50:13 -0400 
>Glyph Lefkowitz <glyph at divmod.com> wrote:
>  
>
>>On Wed, 2004-08-11 at 17:40, James Y Knight wrote:
>>    
>>
>
>  
>
>>So, PyOpenSSL should plug into the reactor as a transport, but all
>>other (saner) Python SSL implementations ought to plug in as a
>>protocol.
>>    
>>
>
>Ahem.  SSL in this parlance is just a TCP connection form with more
>dependencies (keys) failure modes (negotiation failures).  The protocol
>that flows over the SSL/TCP connection is arbitrary (eg HTTP, telnet,
>SMTP, etc).
>
>  
>
I have to agree.

Conceptually Secure Socket Layer is a special kind of socket. You never 
open a SSL connection by itself - you open a FTP session over SSL.

Implementing SSL as a protocol means that inside Twisted you will 
probably have to somehow chain two protocols  together  i.e. ftp  -> 
ssl  before you transport.

===============================================
Web                 -> www.reedflute.com
=============================================== 






More information about the Twisted-Python mailing list