[tor-dev] high latency hidden services
michael at briarproject.org
Mon Jan 5 19:17:46 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
On 04/01/15 09:45, grarpamp wrote:
>> That tells you how much chaff to send in total, but not how much
>> to send on each link.
> No. Buy or allocate 1Mbit of internet for your tor. You now have to
> fill that 1Mbit with tor. So find enough nodes from consensus who
> also have a need to fill some part of their own quota and start
> passing fill with them.
> You'd have to think about whether to use one of them as your own
> guard or make another filled connection to your real guard.
To be clear, are you suggesting that each relay and each client should
pick some relays from the consensus and exchange chaff with them, and
clients should also exchange chaff with their guards?
If that's what you're suggesting, then what happens if a client wants
to extend a circuit from relay A to relay B, but A and B aren't
exchanging chaff with each other?
>> The amount of wheat+chaff on each link must change in response to
>> the amount of wheat.
> Of course, wheat occupies space in a stream of buckets you'd
> otherwise be filling with chaff.
Are you saying that wheat can only be sent over links that have been
chosen to carry chaff?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the tor-dev