[Git][NTPsec/ntpsec][master] Tweaks to TODO(SHM) and TODO-NTS
Hal Murray
gitlab at mg.gitlab.com
Fri Nov 22 08:10:21 UTC 2019
Hal Murray pushed to branch master at NTPsec / ntpsec
Commits:
cadd1c1e by Hal Murray at 2019-11-22T08:09:12Z
Tweaks to TODO(SHM) and TODO-NTS
- - - - -
2 changed files:
- devel/TODO-NTS
- devel/TODO.adoc
Changes:
=====================================
devel/TODO-NTS
=====================================
@@ -1,8 +1,3 @@
-For Release:
- Fix SecondsPerDay in nts_cookie.c
- It is set to 3600 for testing
- That makes too-old cookies if the polling interval is long enough
-
BUGS:
timeout on client connect too long (system default)
Is 3 seconds timeout OK? (both client and server)
@@ -10,14 +5,10 @@ BUGS:
nts_log_ssl_error() No SSL param ??
ERR_error_string_n
-multithread msyslog
- I think this has been fixed.
-
Hourly logging?
ntpq get totals vs recent
documentation:
- HOWTO on NTS
HOWTO on certificates
glossary: https://letsencrypt.org/docs/glossary/
@@ -37,4 +28,3 @@ client certificates
Pool/cluster mode
?? Ratchet for new cookie key
-
=====================================
devel/TODO.adoc
=====================================
@@ -23,6 +23,15 @@ __________
Also see https://gitlab.com/NTPsec/ntpsec/issues/68 where the dubiousness
of the current startup logic gets discussed.
+=== SHM ===
+
+* Split out the low level code so it can be used by other drivers
+ and a monitor program.
+
+* Fix the code so that the read side is read-only. This allows
+ multiple readers and cleans up the file access mess.
+
+
=== Future plans ===
* Implement Google's proposed standard smear?
@@ -62,10 +71,6 @@ of the current startup logic gets discussed.
go to an event-queue architecture that wakes the daemon up just in time
for the next scheduled event (rather than a once-per-second timer tick).
-* Take another look at SHM. Hal thinks we can make a version that is
- read-only and solid. Maybe write a support package that does all the
- work if you call it with the date/time.
-
Plug restrict holes:
The current code pokes a hole in any restrictions to let servers
through if they come from DNS lookups. We should add something like
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/cadd1c1e3cedf766df1cc428b443e9e1459612fb
--
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/cadd1c1e3cedf766df1cc428b443e9e1459612fb
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20191122/732745f2/attachment-0001.htm>
More information about the vc
mailing list