Skip to content
GitLab
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
ntpsec
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
NTPsec
ntpsec
Commits
ea5f9a21
There was a problem fetching the pipeline summary.
Commit
ea5f9a21
authored
7 years ago
by
Eric S. Raymond
Browse files
Options
Downloads
Patches
Plain Diff
Remove obsolete TODO items.
parent
13398c9e
No related branches found
No related tags found
Loading
Pipeline
#
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
devel/TODO
+0
-8
0 additions, 8 deletions
devel/TODO
with
0 additions
and
8 deletions
devel/TODO
+
0
−
8
View file @
ea5f9a21
...
...
@@ -39,16 +39,8 @@ of the current startup logic gets discussed.
* Test that the pool code properly replaces a server if it goes dark. (Not
clear how to arrange this.)
* ntpd is remarkably bad at standalone Stratum 1 - requires multiple chimers
(and multiple inbound NTP connections, and a hole in your firewall) even when
it has a known-good local timesource like a GPS. This should be fixed.
* Full support for NTS, once IETF has the spec ready
* All the code relating to iteration over interfaces can and should be removed
in favor of binding to wildcard addresses. Information on how to do this
us here: https://blog.powerdns.com/2012/10/08/on-binding-datagram-udp-sockets-to-the-any-addresses/
* We could open only IPv6 sockets and allow them to handle mapped IPv4 addresses,
as described at http://man7.org/linux/man-pages/man7/ipv6.7.html
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment