-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Scott,
> 
> This looks cool, but can you outline exactly what you have done?  I am
> assuming that this addresses the issue of inter-node encryption, but
> what kind of backward compatability/future compatability is in there?

As it stands right now, I've backed the hooks out because I'm pretty sure
they aren't in the right place.  We haven't worked out a means of backward
compatibility, because that would require that the old clients negotiate
crypto, which isn't backwards. :)  So the code to hook to the server that
I *had* in there assumed crypto every time, using a shared Diffie Helman
public key.  

I just finished implementing Hal's modified CFB, (I call it Periodic CFB,
or PCFB), and am ready to bring it into the server as soon as we decide
where it needs to go.  

Last night, with the old code, I tested a couple of servers with the
always-on-crypto.  Apart from the problems with padding that I outlined
(which aren't a problem with PCFB) it worked like a charm.

        Scott


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE5EECLpXyM95IyRhURAgFrAJ43xmBrl0FrfRAOl5IKAv1GF9hu7ACgph9X
qNUcEc5cx9wNcwLs1siiryk=
=7dc9
-----END PGP SIGNATURE-----


_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev

Reply via email to