Re: E / Python interoperability suggestions?

On Thu, 2010-09-02 at 06:15 -0400, Kevin Reid wrote:
> On Sep 1, 2010, at 21:15, Bill Frantz wrote:
> 
> > Assuming we want to adopt the TLS protocol and implement it in
> > E, we will need a bunch of crypto primitives. From memory they are:
> >
> >    MD5 + SHA1 - For the TLS pseudo random function
> >    A digital signature algorithm - currently DSA (uses SHA1)
> >    A Diffie-Hellman implementation - Currently in Java using a
> > prime field
> >    A symmetric encryption algorithm - Currently triple DES
> ...
> > The above gives us the maximum portability. Any E implementation
> > which can provide the basic network listen, call, send, and
> > receive automatically has E communication.
> 
> I had assumed that TLS was a canned protocol we could use outside  
> libraries to implement; I seem to recall old discussion about 'the  
> only reason we can't adopt TLS is that the common library/ies doesn't  
> let us read the key fingerprint' which then became false.

Yes, I thought being able to use the platform's SSL support was the main
point of this. I can't see why E should care what symmetric algorithm is
used for example; the two endpoints should negotiate that by themselves
using the system SSL libraries, which are kept up-to-date by the OS
distributor.


-- 
Dr Thomas Leonard
IT Innovation Centre
2 Venture Road
Southampton
Hampshire SO16 7NP

Tel: +44 0 23 8076 0834
Fax: +44 0 23 8076 0833
mailto:tal-v5nx5w6akNyLE8xUarVfuPLx9OUvmyODWmv/[email protected]
http://www.it-innovation.soton.ac.uk