![]() There are some cases where it doesn't seem to help: if an attacker can watch all of your incoming and outgoing traffic, then it's easy for them to learn which connections were relayed and which started at you. They will see a connection from you, but they won't be able to know whether the connection originated at your computer or was relayed from somebody else. The simplest example is an attacker who owns a small number of Tor relays. Yes, you do get better anonymity against some attacks. You need to copy / backup both of them in order to restore your relay, change your DataDirectory or migrate the relay on a new computer. Until then, each relay will have both an ed25519 identity (identity key file: keys/ed25519_master_id_secret_key) and a RSA identity (identity key file: keys/secret_id_key). Note: As of Tor 0.2.7 we are using new generation identities for relays based on ed25519 elliptic curve cryptography.Įventually they will replace the old RSA identities, but that will happen in time, to ensure compatibility with older versions. It contains data required for your bridge to keep working with the same bridge line. ![]() If you are a bridge operator, also make sure to copy pt_state/. ![]() If you need to pick a new DataDirectory, be sure to copy your old keys/ed25519_master_id_secret_key and keys/secret_id_key over. ![]() This means that if you're upgrading your Tor relay and you keep the same torrc and the same DataDirectory, then the upgrade should just work and your relay will keep using the same key. ![]() Keeping backups of the identity keys so you can restore a relay in the future is the recommended way to ensure the reputation of the relay won't be wasted. When upgrading your Tor relay, or moving it on a different computer, the important part is to keep the same identity keys (stored in "keys/ed25519_master_id_secret_key" and "keys/secret_id_key" in your DataDirectory). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |