Opened 5 years ago

Last modified 2 years ago

#13494 new enhancement

Regression test about Hidden Service time synchronization

Reported by: asn Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7
Severity: Normal Keywords: tor-hs, tests, clock, clock-sync, ntp, needs-diagnosis
Cc: Actual Points:
Parent ID: Points: 6
Reviewer: Sponsor:

Description

People in IRC yesterday were wondering what causes HS circuits to fail if the clocks of both parties are not synchronized. Apparently HS circuits should work even with desynchronized clocks these days.

There was disagreement about that, and Roger suggested writing a regression test to make sure that if HSes don't need time synchronization right now they will keep on working without it in the future too.

This falls under the larger SponsorR framework of being able to more easily benchmark and test Hidden Services.

Child Tickets

Change History (18)

comment:1 Changed 5 years ago by cypherpunks

Tor itself doesn't work if the clock is too inaccurate.

comment:2 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-final

comment:3 Changed 4 years ago by nickm

Status: newassigned

comment:4 Changed 4 years ago by nickm

Keywords: 027-triaged-1-in added

Marking more tickets as triaged-in for 0.2.7

comment:5 Changed 4 years ago by isabela

Keywords: SponsorS added
Points: medium/large
Version: Tor: 0.2.7

comment:6 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.8.x-final

comment:7 Changed 4 years ago by nickm

Keywords: SponsorR removed
Sponsor: SponsorR

Bulk-replace SponsorR keyword with SponsorR sponsor field in Tor component.

comment:8 Changed 4 years ago by dgoulet

Keywords: 027-triaged-1-in removed

comment:9 Changed 4 years ago by dgoulet

Sponsor: SponsorRSponsorR SponsorS

comment:10 Changed 4 years ago by dgoulet

Keywords: tests added; tor-tests SponsorS removed
Type: projectenhancement

comment:11 Changed 3 years ago by nickm

Priority: MediumLow

comment:12 Changed 3 years ago by dgoulet

Milestone: Tor: 0.2.8.x-finalTor: 0.2.???
Severity: Normal

comment:13 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:14 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:15 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:16 Changed 2 years ago by nickm

Status: assignednew

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

comment:17 Changed 2 years ago by dgoulet

Points: medium/large6
Sponsor: SponsorR SponsorS

comment:18 Changed 2 years ago by nickm

Keywords: clock clock-sync ntp needs-diagnosis added
Note: See TracTickets for help on using tickets.