[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: HidServDirectoryV2 option
-----BEGIN PGP SIGNED MESSAGE-----
Hi Olaf and all,
| recently I was told about the HidServDirectoryV2 server option. So far
| only four nodes accept and serve v2 hidden service descriptors:
| => gpfTOR1, gpfTOR3, gabelmoo, and my own node blutmagie
| Are there any known drawbacks with HidServDirectoryV2?
Known drawbacks? No. Bugs? Maybe, but none that we know about.
We did not publicly announce this new config option yet, because there
was still some code about v2 hidden service descriptors that needed to
be included in trunk. But since last night (!) everything is in.
So, what happens when you set "HidServDirectoryV2 1"? Your relay will
become part of a DHT-like directory for hidden service descriptors.
Hidden servers with version 0.2.0.10-alpha or higher publish their
descriptors to a subset of these relays in addition to (some day:
instead of) the directory authorities. And clients with version
0.2.0.10-alpha or higher fetch descriptors from those relays in parallel
to (some day: instead of) fetching descriptors from the directory
authorities. The idea is to have a large number of relays having that
config option set, e.g. some hundreds.
So, if your relay has a current alpha version (0.2.0.16-alpha or
higher), please consider adding that config option. The more the better.
Note: Your relay needs to run for at least 24 hours before being listed
as hidden service directory in the Tor status.
If you want to learn more about v2 hidden service descriptors, have a
look at proposal 114:
Again, no guarantees that there are no bugs anymore. But without testing
we won't find them.
So, I would suggest: Let the testing begin! :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----