[tor-dev] Hidden Service Scaling

[Michael Rogers]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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?

Cheers,
Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCAAGBQJTbOyoAAoJEBEET9GfxSfMOFcH/3AVyEinJd5AP6TkhpRBJVLE
25cm8EaY/G8cNFMAW4qDDR0o8iTonlJwsxvA5j8DGh6nejrSdf+pKLcO2W+uCCHf
lKm7l0yoirc4camB+5Qh1EIiYa3ABMbagCvtqaSpI3bchOs6+bMsS/Aw2VLbVLzr
mttc2GJbtAxrQl7cSN5Kq24ZJ+I7lHDqCMxCm9CyTKN/s51T0+SQzC++2v24SAoP
DqKBJHm1Kn5tU0XDt0BiK2hF7C0NXDWVe/eGJ0oyZ0vdJmBSfcfzZW2/6LnIrpCE
kmQfFt3HI1O2tVvXyXvrGRpN5jDTQ/qNvuLGetTkmeyXQrZzauXTw+BoyhCD1Oo=
=P0vo
-----END PGP SIGNATURE-----