[tor-dev] Revisiting prop224 time periods and HS descriptor upload/downloads

George Kadianakis desnacked at riseup.net
Sun May 8 21:39:09 UTC 2016


George Kadianakis <desnacked at riseup.net> writes:

> [ text/plain ]
> David Goulet <dgoulet at ev0ke.net> writes:
>
>> [ text/plain ]
>> On 13 Apr (15:34:54), George Kadianakis wrote:
>>> David Goulet <dgoulet at ev0ke.net> writes:
>>> 
>>> > [ text/plain ]
>>> > On 12 Apr (16:01:32), George Kadianakis wrote:
>>> >> David Goulet <dgoulet at ev0ke.net> writes:
>>> >> 
>>> >> > [ text/plain ]
>>> >> > On 11 Apr (14:42:02), George Kadianakis wrote:
>>> >> >> David Goulet <dgoulet at ev0ke.net> writes:
>>> >> >> 
>>> >> >> > [ text/plain ]
>>> >> >> > On 04 Apr (19:13:39), George Kadianakis wrote:
>>> >> >> >> Hello,
>>> >> >> >> 
>>> >> >> >> during March we discussed the cell formats of prop224:
>>> >> >> >>   https://lists.torproject.org/pipermail/tor-dev/2016-March/010534.html
>>> >> >> >> 
>>> >> >> >> The prop224 topic for this month has to do with the way descriptors get
>>> >> >> >> uploaded and downloaded, how this is scheduled using time periods and how the
>>> >> >> >> shared randomness subsystem interacts with all that.
>>> >> >> >> 
>>> >> >> >> <snip>
>>
>>> 
>>> Here are some things left to be done:
>>> 
>>> - Specify *when* hidden services upload descriptors. Do they do it hourly, or
>>>   only when a change has happened. Both approaches leak information to the
>>>   HSDir (the former leaks uptime, the latter leaks intro point changes).
>>
>> I'm more comfortable right now with the HS uploading every RendPostPeriod
>> (default: 1 hour). Even if the descriptor content doesn't change, it should
>> increment the revision-counter.
>>
>> I'm more and more convinced that making RendPostPeriod _not_ configurable is
>> also something we should do and thus allowing us to have the HSDir use that
>> value instead (maybe).
>>
>
> Hello,
>
> I pushed some more changes to my `prop224-timeperiods-1` branch.
>

Merged the `prop224-timeperiods-1` branch to torspec master.

Thanks for the review and comments!



More information about the tor-dev mailing list