Sebastian Hahn commited on 2016-02-27 06:45:40
Zeige 1 geänderte Dateien mit 70 Einfügungen und 4 Löschungen.
Wording mostly s7r's from the ticket.
... | ... |
@@ -188,6 +188,8 @@ be?</a></li> |
188 | 188 |
relay?</a></li> |
189 | 189 |
<li><a href="#UpgradeOrMove">I want to upgrade/move my relay. How do I |
190 | 190 |
keep the same key?</a></li> |
191 |
+ <li><a href="#OfflineED25519">How do offline ed25519 identity keys work? |
|
192 |
+ What do I need to know?</a></li> |
|
191 | 193 |
<li><a href="#MultipleRelays">I want to run more than one |
192 | 194 |
relay.</a></li> |
193 | 195 |
<li><a href="#NTService">How do I run my Tor relay as an NT service? |
... | ... |
@@ -2733,15 +2735,79 @@ lots |
2733 | 2735 |
How do I keep the same key?</a></h3> |
2734 | 2736 |
|
2735 | 2737 |
<p> |
2736 |
- When upgrading your Tor relay, or running it on a different computer, |
|
2737 |
- the important part is to keep the same identity key (stored in |
|
2738 |
- "keys/secret_id_key" in your DataDirectory). |
|
2738 |
+When upgrading your Tor relay, or moving it on a different computer, the |
|
2739 |
+important part is to keep the same identity keys (stored in |
|
2740 |
+"keys/ed25519_master_id_secret_key" and "keys/secret_id_key" in your |
|
2741 |
+DataDirectory). Keeping backups of the identity keys so you can restore |
|
2742 |
+a relay in the future is the recommended way to ensure the reputation of |
|
2743 |
+the relay won't be wasted. |
|
2739 | 2744 |
</p> |
2745 |
+ |
|
2740 | 2746 |
<p> |
2741 | 2747 |
This means that if you're upgrading your Tor relay and you keep the same |
2742 | 2748 |
torrc and the same DataDirectory, then the upgrade should just work and |
2743 | 2749 |
your relay will keep using the same key. If you need to pick a new |
2744 |
-DataDirectory, be sure to copy your old keys/secret_id_key over. |
|
2750 |
+DataDirectory, be sure to copy your old |
|
2751 |
+keys/ed25519_master_id_secret_key and keys/secret_id_key over. |
|
2752 |
+</p> |
|
2753 |
+ |
|
2754 |
+<p> |
|
2755 |
+Note: As of Tor 0.2.7 we are using new generation identities for relays |
|
2756 |
+based on ed25519 elliptic curve cryptography. Eventually they will |
|
2757 |
+replace the old RSA identities, but that will happen in time, to ensure |
|
2758 |
+compatibility with older versions. Until then, each relay will have both |
|
2759 |
+an ed25519 identity (identity key file: |
|
2760 |
+keys/ed25519_master_id_secret_key) and a RSA identity (identity key |
|
2761 |
+file: keys/secret_id_key). You need to copy / backup both of them in |
|
2762 |
+order to restore your relay, change your DataDirectory or migrate the |
|
2763 |
+relay on a new computer. |
|
2764 |
+</p> |
|
2765 |
+ |
|
2766 |
+ |
|
2767 |
+ <hr> |
|
2768 |
+ |
|
2769 |
+<a id="OfflineED25519"></a> |
|
2770 |
+<h3><a class="anchor" href="#OfflineED25519">How do offline ed25519 |
|
2771 |
+identity keys work? What do I need to know?</a></h3> |
|
2772 |
+ |
|
2773 |
+<p> |
|
2774 |
+As of Tor 0.2.7 offline ed25519 identity keys are supported. In simple words, it works like this: |
|
2775 |
+<ul> |
|
2776 |
+<li>there is a master ed25519 identity secret key file named |
|
2777 |
+"ed25519_master_id_secret_key". This is the most important one, so make |
|
2778 |
+sure you keep a backup in a secure place - the file is sensitive and |
|
2779 |
+should be protected. Tor could encrypt it for you if you generate it |
|
2780 |
+manually and enter a password when asked.</li> |
|
2781 |
+ |
|
2782 |
+<li>a medium term signing key named "ed25519_signing_secret_key" is |
|
2783 |
+generated for Tor to use. Also, a certificate is generated named |
|
2784 |
+"ed25519_signing_cert" which is signed by the master identity secret key |
|
2785 |
+and confirms that the medium term signing key is valid for a certain |
|
2786 |
+period of time. The default validity is 30 days, but this can be |
|
2787 |
+customized by setting "SigningKeyLifetime N days|weeks|months" in |
|
2788 |
+torrc.</li> |
|
2789 |
+<li>there is also a master public key named |
|
2790 |
+"ed25519_master_id_public_key, which is the actual identity of the relay |
|
2791 |
+advertised in the network. This one is not sensitive and can be easily |
|
2792 |
+computed from "ed5519_master_id_secret_key".</li> |
|
2793 |
+</ul> |
|
2794 |
+Tor will only need access to the medium term signing key and certificate |
|
2795 |
+as long as they are valid, so the master identity secret key can be kept |
|
2796 |
+outside DataDirectory/keys, on a storage media or a different computer. |
|
2797 |
+You'll have to manually renew the medium term signing key and |
|
2798 |
+certificate before they expire otherwise the Tor process on the relay |
|
2799 |
+will exit upon expiration. |
|
2800 |
+</p> |
|
2801 |
+ |
|
2802 |
+<p> |
|
2803 |
+This feature is optional, you don't need to use it unless you want to. |
|
2804 |
+If you want your relay to run unattended for longer time without having |
|
2805 |
+to manually do the medium term signing key renewal on regular basis, |
|
2806 |
+best to leave the master identity secret key in DataDirectory/keys, just |
|
2807 |
+make a backup in case you'll need to reinstall it. If you want to use |
|
2808 |
+this feature, you can consult our <a |
|
2809 |
+href="https://trac.torproject.org/projects/tor/wiki/doc/TorRelaySecurity/OfflineKeys">more |
|
2810 |
+detailed guide</a> on the topic. |
|
2745 | 2811 |
</p> |
2746 | 2812 |
|
2747 | 2813 |
<hr> |
2748 | 2814 |