-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > How do you propose maintaining backward compatibility? > > > > > Local data encrpytion using the plaintext keys > > Ditto. This is a client issue, probably a 20 minute job if we decide on a > > cipher. > > Again, we need to be clear on how backward compatibility is maintained. Well, unfortunately, there really isn't an idea of backward compatibility in crypto. If we switch ciphers, all that data is useless to clients that don't support it. We might consider a metadata field that informs the client which cipher was used when the data was inserted, since doing so doesn't harm the security any.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5CF1ppXyM95IyRhURAsidAJ9b6Nah40E6N6APoMfZjHgBK8HSrQCdEdON 0idkc/6HTn5GGnbtHxWGd4A= =ZylO -----END PGP SIGNATURE----- _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
