[Remops] Best practice for implementing new remailer keys

[Bergman Remailer Admin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 05/11/13 04:43 PM, lists at notatla.org.uk wrote:
> 
>> Can Mixmaster (my version is 2:3.0.1b) handle having two mix
>> keys, old and new, in its key.txt and secring.mix files for the
>> switchover period of, say, 14 days?
> 
> The key data necessary is in secring.mix (for both/all keys) and
> the key.txt is generated from that showing just the new key.  After
> the overlap period old versions keep the expired key in the file.

This is helpful to know. Thank you.

> (It's one of my extensions to delete the old key data from the
> file so it can't fall into the hands of someone wishing to use it
> to recover old messages.)

Your key agility feature is an exciting development. And I intend to
upgrade my Mixmaster version in preparation for it's roll out. This is
the primary reason I was asking about the correct way to switchover when
generating new keys.

I'm also happy to know that Mixmaster developers like yourself and Steve
are working on beefing up the current 1024 bit key size. I know end
users will be very happy with this as well.


Bergman Remailer Admin 0x770251F2
Fingerprint: 8124 C17B 7FD9 1738 066F 4E29 4407 A967 7702 51F2
http://bergman.delphy.org/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCAAGBQJSeYd0AAoJEEQHqWd3AlHyYncIAKM0qkAYbBzWcXFnVIajIvZP
kGGMLFcrGEfUWF6VpvHl7a3tmAWmwgFYaTvoPwJuiCWjYDIMhkmPEy/6p9IxrwRr
+4GUxy4O4LsCwDYG/8IykEZcnd9ansBk8MBd9FEZpTX8fR7oGjimghxTgv4sH2HJ
BdF6F2p2PYyVJhiSyuzkj8MusxV33pDBOSSdp9F+Z5JBudkBmkyL8wPl9eEw69PP
hI9zDu0SOYzKVUGfGgpA3qQtDklXfw2ClWh6G/y4n/9XiKCm/d+/Li8HFFM3Z6uh
kFYpSDjfkvjYXiVE+kjXHoDO1xKgmwU9TEQ2wzxnKNUhfksy7NQVcz/LnnihClc=
=210m
-----END PGP SIGNATURE-----