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
