Project

General

Profile

Bug #11574

Investigate security consequences of restarting htpdate until it succeeds

Added by bertagaz over 3 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Time synchronization
Target version:
-
Start date:
07/17/2016
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Description

While implementing #10494, concerns were raised if restarting htpdate wouldn't just break one of its main goal, which is to fail if one of its pool seems to be compromised because it reached allowed_per_pool_failure_ratio.

Before deciding what to do with #10494, we should research about its security consequences.


Related issues

Blocks Tails - Bug #10494: Retry htpdate when it fails Rejected 07/17/2016

History

#1 Updated by bertagaz over 3 years ago

  • Blocks Bug #10494: Retry htpdate when it fails added

#2 Updated by intrigeri over 3 years ago

(Same as ticket blocked by this one.)

#3 Updated by intrigeri over 3 years ago

You can move that to 2.6 if you wish.

#4 Updated by bertagaz over 3 years ago

  • Target version changed from Tails_2.5 to Tails_2.6

#5 Updated by anonym over 3 years ago

  • Target version changed from Tails_2.6 to Tails_2.7

#6 Updated by bertagaz over 3 years ago

  • Status changed from Confirmed to Rejected
  • Assignee deleted (bertagaz)
  • Target version deleted (Tails_2.7)

As discussed in #10495#note-50, endless retries of htpdate won't be the way we choose. So it's not necessary to raise the question this ticket is about, which sounded bad at first glance anyway. Closing it.

#7 Updated by intrigeri over 3 years ago

JFTR I think you mean #10494#note-50.

#8 Updated by bertagaz over 3 years ago

intrigeri wrote:

JFTR I think you mean #10494#note-50.

Right, I did, thanks!

Also available in: Atom PDF