I really don't think it is worth the effort to try to keep the implementation of crypto from breaking the protocol. We have a couple of other features coming up that will require a new protocol anyways. If Ian goes ahead and does a release on Monday, people will have a fairly stable node to play with, and then we can move the protocol to 1.3 in the CVS and get the freedom to make changes back for a while.
With the next release after Monday's we then introduce a new more or less finished protocol with support for encryption and keytypes, the new message names, etc (say protocol 1.5). This protocol should be good enough to last for several months, hopefully until we get to a 1.0 release of the node. On Thu, 27 Apr 2000, hal at finney.org wrote: > On Thursday, Apr 27, 2000, "Scott G. Miller" writes: > >I can take this one in the manner Oskar suggested. I've already completed > >a key exchange and socket crypto layer. Its just a matter of hooking it > >up to freenet at the connection layer. > > I assume that either the server or the client would have to send some kind > of message to initiate the key exchange negotiation? So there would be > a backwards compatibility issue here, in the event that the other side > does not understand the key exchange request message. In that case it > would be good if the node could fall back on an unencrypted connection. > > It's not clear to me how or whether this would all be done in the socket > layer. For example we could have the handshake message return a field > telling whether the node supports encryption. But in that case the > client would not turn on encryption until after handshaking. > > I'd like to hear more about how the protocol would work in terms of the > socket layer data handling versus the higher layer. SSL for example > handles this by specifying a different port number for the "secure" > versions of the protocols. This makes sure there is no conflict where > non-secure-aware software has to try to handle messages from peers > requesting security services. > > Hal > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev -- Oskar Sandberg md98-osa at nada.kth.se #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1 lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
