[tor-dev] prop224: "revision-counter" field leaks service/intro point stability

[Tim Wilson-Brown - teor]

Hi all,

The hidden service descriptor's "revision-counter" field is incremented every time the descriptor is updated.

I wonder what the distribution of these versions will be:
* a hidden service with a value of 0 (or 1) has just started up (or just rolled over to a new period)
* an unstable hidden service might have an unusually high count
* if enough introduction points go down or are DoSed, the hidden service will find new ones, and increment the count

Should we randomise the start value and increment?
How can we do this in a way that doesn't lead to exhaustion of the revision-counter?

Tim

Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP 968F094B

teor at blah dot im
OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20151118/f01e8bd9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20151118/f01e8bd9/attachment-0001.sig>