diff options
Diffstat (limited to 'wiki/src/contribute/design')
| -rw-r--r-- | wiki/src/contribute/design/Time_syncing.mdwn | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/wiki/src/contribute/design/Time_syncing.mdwn b/wiki/src/contribute/design/Time_syncing.mdwn index 4a9234b..1a9fbd9 100644 --- a/wiki/src/contribute/design/Time_syncing.mdwn +++ b/wiki/src/contribute/design/Time_syncing.mdwn @@ -90,10 +90,10 @@ Third, things are different depending on if you're using a bridge or not. If not using a bridge: Tails starts without a cached consensus, so its -Tor client starts by connecting directly to a directory authority (and -not to a directory mirror / entry guard), so feeding you an old +Tor client starts by connecting directly to a fallback directory +mirror, so feeding you an old consensus requires the attacker either to break SSL, or to control the -directory authority your Tor client connects to. Not good, but +fallback directory mirror your Tor client connects to. Not good, but probably a compromise we can make. If using a bridge: your bridge can replay an old (one week old max.) |