-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 18/01/15 19:02, Patrick Scharmer wrote: > Hi, > > I’ve been running a bridge for over a year and noticed recently > that the fingerprint shown in ARM (and that actually works when > connecting to the bridge) differs from the fingerprint displayed > for my bridge on both Atlas and Globe. Any thoughts on why this > would happen and how to fix it? I’m assuming the fingerprint > published on Atlas & Globe is the same fingerprint that will be > distributed by bridges.torproject, is that correct?
arm displays your bridge's fingerprint, which is also distributed by bridges.torproject.org. Atlas and Globe show your bridge's *hashed* fingerprint. The reason that they're not showing the (non-hashed) fingerprint is that anyone could ask the bridge authority for your bridge's current descriptor if they had its (non-hashed) fingerprint, and that would reveal your bridge's IP address. That's why Atlas and Globe hash your fingerprint. > Apologies if this is a common question… I’ve only recently joined > the mailing list and couldn’t find a way to search the archives > other than browsing. It's a valid question. If you have any ideas how to explain it better on Atlas or Globe, please open a ticket. Thanks! All the best, Karsten -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJUvLSXAAoJEJd5OEYhk8hIMTMIAJN5OUo7NDNNWzq/0nfdkbDg qxfNDLPp2xaW6uLP2kXOrNKraO/N5BgHJ7qKm0SuEVLLac+PHKWJuIiulfWNXfrc Bx6f1YSAydUtHqoc7sVGXTG5APxFV218nQjby06xMy+cWbw9Wyy3tzoen47okqCX RMOTgwyz462rBwujFDu3Jt0gY85CuMEauaKMd49chLreT2d2X/kdhJz8sl0X3xpr On1KwUBZIXKzqQRHmFbJxMHkSjXoK4xd4Sj2llLUkQ5uK1mlye7vxBEKpcO53Cwo tJ10eZdmgPzmuoesCZiv9W9vQDR0shV+ZiIIGe72YRHpX4lBEINaXOGPz6Vrzdc= =lIYh -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays