[tor-dev] is the consensus document unpredictable / unique?

s7r s7r at sky-ip.org
Sat Jun 25 22:52:41 UTC 2016

Hello again,

I am sorry, too tired and written something wrong:

On 6/26/2016 1:29 AM, s7r wrote:
> Very soon Tor will include an unique random value we call "Consensus
> Shared Randomness [SRVALUE]" in every consensus, you can just use that.
> This is proposal 250. This seams like a better standardized upstream
> solution with infinite better security properties, so I'd use this as a
> cookie. This has the advantage of having the same unique value on all
> nodes all the time: just filter and pair consensus SRVALUE + consensus
> valid-after timestamp and everyone will be requesting the SRVALUE of the
> same consensus, therefor producing the same result or fail if none.

This is not true. The SRVALUE will be the same for an entire day. So you
still need to hash the entire consensus if you need an unique value for
_every_ consensus or use SRVALUE if you need an unique value for a day.
Sorry again for not double reading my previous email.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20160626/d5c94217/attachment-0001.sig>

More information about the tor-dev mailing list