jchase transcribed 0.6K bytes:

Hello, I have a bridge up and running for about 6 months. I have two questions. According to arm my fingerprint is 72DB4EE86C65856E3131A32D8E30EC8A2B72A73D . But if I look up rasptorholland in globe.torproject.org I find that my fingerprint is 1BCD3EBEFE17EEB86EEDE21D5E2DB8468E2864CF .

Globe replaces Bridge fingerprints with their hashed form, i.e. instead of:

72DB4EE86C65856E3131A32D8E30EC8A2B72A73D = H(PK_ID)

It's hashed again, i.e.:

1BCD3EBEFE17EEB86EEDE21D5E2DB8468E2864CF = H(H(PK_ID))

This is to protect the real fingerprint of the Bridge, because with the real fingerprint one can request its descriptor and connect to it (meaning that leaking the fingerprint can result in the Bridge being blocked in censoring regions).

And again according to globe.torproject.org my pool assignment is blank (the empty set). Are these related to each other and is something wrong? Thanks, J Chase

BridgeDB no longer syncs pool assignment data to the Metrics servers, [0] meaning that it no longer ends up in Onionoo, meaning that it no longer ends up in Globe.

There is ticket #13921 to remove this field from Globe's display.

Patches, reviews of others' patches, and other contributions to Globe are *extremely* welcome, as I hate writing JS and detest the web.

[0]: https://bugs.torproject.org/14082 [1]: https://bugs.torproject.org/13921