ntp-project / ntp Goto Github PK

Configuration method reference：
http://support.ntp.org/bin/view/Support/ConfiguringAutokey

The project may be assuming some old project building convention related to autotools that not everyone is familiar with especially people who are more familiar with other build tools, or maybe the documentation is just out-of-date.

Particularly, INSTALL refers to a file called 'configure' which does not exist. INSTALL also talks about running autoconf to generate configure from configure.in, but configure.in doesn't exist, either. There is configure.ac but there is no mention of it.

The biggest problem is that configure is missing. Normally, people run configure followed by make. Maybe there is some unspoken rules about how to generate configure from some other files that people familiar with autotools would know, but this is not generally clear to me. Since the last commit is 2016, maybe this repo is unmaintained?

Why do you have to wait 5 minutes for the local clock ntpd to be accessible by the clients？

We know that max seconds of transmiting message updating time among different clients by the ntp are 2^32 seconds, but time difference are only 2 years between server and clinet actually. So I do not know how is it ? Can someone give me some suggestions, thank you in advance！

File: https://github.com/ntp-project/ntp/blob/master-no-authorname/ntpd/ntp_control.c contains CVE-2015-8139.
Look here: ntpsec/ntpsec@aa11b6a

The site display:

503 Service Unavailable

No server is available to handle this request.

At time 2020-03-24 08:00 UTC

I had that amazing moment today at NTP.ORG. I check the localization subdomain time server and tried "us.pool.ntp.org" and a video's page redirects to me. so funny :)

While looking at the licenses of the files, I noticed that the file is licensed GPLv3+.
(/sntp/libopts/m4/libopts.m4)
Therefore, when building with static linking, this license is transferred to the entire package, as far as I understand.
Looking through the library versions for the same file, I didn't find this license.
If you have the opportunity, could you add an exception.(https://spdx.org/licenses/Autoconf-Exception-macro.html)
or explicitly indicate this nuance.

https://github.com/ntp-project/ntp/blob/9c75327c3796ff59ac648478cd4da8b205bceb77/ntpd/refclock_shm.c#L606C8-L606C8

/* check 1: age control of local time stamp */
tt = shm_stat.tvc.tv_sec - shm_stat.tvr.tv_sec;
if (tt < 0 || tt > up->max_delay) {
	DPRINTF(1, ("%s:SHM stale/bad receive time, delay=%llds\n",
		    refnumtoa(&peer->srcadr), (long long)tt));
	up->bad++;
	msyslog (LOG_ERR, "SHM: stale/bad receive time, delay=%llds",
		 (long long)tt);
	return;
}

Here we substract received time stamp from current local time stamp (tt variable). If received time stamp is greater (which means that we should move system clock forward), we get negative value in tt. Further, we check if tt is negative ( tt < 0) and refuse to do such time adjustment. Is it correct behaviour? Error message for such case claims that received time stamp is stale, i.e. the received time is older than current time, which conflicts with actual actions in code. It is a common case that hardware without power support on local RTC clock will get in such scenario, that received time stamp from some external time source is newer than local time stamp. The reverse case seems to be unrealistic. And it is protected by tt > up->max_delay check, as far as i see.

I would like to make a contribution to the ntp project, but noticed that the github repository hasn't been updated for three years.

I have not worked with Bitkeeper before as Bitkeeper has traditionally been a commercial software and git has been the tool of choice for years now for most developers.

Would it be possible to keep the git repository in sync with Bitkeeper or even switch to git on github completely?

When I set the time on the NTP server to the year 2000 and the client's time to the correct year 2023, and then use NTPD as the client to synchronize with the server, the client's time is changed to the year 2136

If the NTP server's time is set to the year 2004, the NTP client's time changes to the year 2140, with a difference of 136 years. This issue persists even with the latest version of NTP, version 4.2.8, but is not present when using version 4.2.6p5.

Our vulnerability scanner detected /usr/bin/sntp is vulnerable to the CVE-2016-10195 , ntp using libevent version 2.1.5-beta which is vulnerable , to fix this CVE, libevent should be updated 2.1.6 and higher.

I read INSTALL, there is "configure.ac" I see numerous references to a configure script, but I do not see the script itself.

Hello, after digging through documentation and online posts, I have not found how to use the sntp application as an sntp server... The docs claims that it is possible but at no point explain how to set it up.
I have read the warnings that come with using an sntp server, and in my use case it is acceptable.

How would one go about setting this up? Which part of the code would I need to hack to introduce reading my reference clock?