[tor-dev] Hidden Service Scaling
michael at briarproject.org
Fri May 9 14:56:41 UTC 2014
-----BEGIN PGP SIGNED MESSAGE-----
On 09/05/14 14:31, Christopher Baines wrote:
> How do you see the guards being "scheduled" for replacement?
Two possibilities (there are probably others):
1. Periodically select a new guard by hashing a secret key and the
date, similar to the way HS directories are selected. The HS instances
use the same secret key and therefore pick the same guard.
2. The HS instances communicate with each other to pick a guard to use
in the next period.
> Another issue is how do you get each instance to connect through
> the same guard node?
If they agree on which guard to use, what's to stop them connecting to it?
> I think that it would be fine having per instance guard nodes (1 or
> more). I don't see much significance in it being shared, it also
> seems quite problematic to accomplish.
OK cool - but the instances will still have to coordinate in some way
to pick IPs, no?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the tor-dev