From 121c8161502a1a7b9b3d73c3dfd42c07023b8c5f Mon Sep 17 00:00:00 2001
From: Daniel Micay <daniel.micay@grapheneos.org>
Date: Sun, 30 Jun 2024 11:54:21 -0400
Subject: [PATCH] explain our server time sync setup

---
 static/faq.html | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/static/faq.html b/static/faq.html
index ad56146b..b66c5428 100644
--- a/static/faq.html
+++ b/static/faq.html
@@ -896,7 +896,9 @@
                             by default, and OEMs can choose the priority order). Network time
                             updates are security sensitive since certificate validation depends on
                             having an accurate time, but the standard NTP / SNTP protocols used
-                            across most OSes have no authentication or encryption.</p>
+                            across most OSes have no authentication. Our servers obtain the time
+                            from 6 independent NTP servers with NTS for authentication where at
+                            least 3 servers need to agree on the time for it to be updated.</p>
 
                             <p>We plan to offer a toggle to use the standard functionality instead of
                             HTTPS-based time updates in order to blend in with other devices.</p>