[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [atlas/master] Add instructions for getting bridge hashed fingerprint (#10883)



commit bf7a7ba2d2335ea4dbe54745dab3d68aa8e692cd
Author: Iain R. Learmonth <irl@xxxxxxxx>
Date:   Sun Nov 6 23:31:04 2016 +0000

    Add instructions for getting bridge hashed fingerprint (#10883)
---
 templates/about.html | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/templates/about.html b/templates/about.html
index 75c2e40..c5de6ff 100644
--- a/templates/about.html
+++ b/templates/about.html
@@ -29,6 +29,13 @@ country:us&rdquo;), with specific contact information (e.g.,
 <p>
 You are able to get a detailed view of how the relay is configured. What its exit policy is and all the data that you would normally find in the descriptor.
 </p>
+<h2>Bridges</h2>
+If you are searching for a bridge, you will need to search by the hashed
+fingerprint. This prevents leaking the fingerprint of the bridge when
+searching. You can find this in the <code>hashed-fingerprint</code> file in the
+Tor data directory. On Debian systems, this is in <code>/var/lib/tor</code>
+but may be in another location on your system. The location is specified as
+<code>DataDirectory</code> in your <code>torrc</code>.
 </div>
 
 <div class="span4">

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits