Your message dated Sat, 8 Sep 2018 00:05:51 +0200
with message-id <[email protected]>
and subject line Closing old bugs
has caused the Debian Bug report #806862,
regarding receive: Unexpected origin timestamp from 61.219.119.38
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
806862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806862
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ntp
Version: 1:4.2.8p4+dfsg-3+b1
I saw
12月 02 19:39:46 jidanni5 ntpd[2246]: Soliciting pool server 61.219.119.38
12月 02 19:39:47 jidanni5 ntpd[2246]: Soliciting pool server 61.219.119.41
12月 02 19:39:47 jidanni5 ntpd[2246]: Soliciting pool server 117.56.73.145
12月 02 19:39:48 jidanni5 ntpd[2246]: Soliciting pool server 123.204.45.116
12月 02 19:39:48 jidanni5 ntpd[2246]: Soliciting pool server 123.204.45.116
12月 02 19:39:48 jidanni5 systemd[905]: Time has been changed
12月 02 19:39:48 jidanni5 ntpd[2246]: receive: Unexpected origin timestamp from
61.219.119.38
http://www.cs.bu.edu/~goldbe/NTPattack.html says
Attack 1 and Attack 2 (Denial of Service). Upgrade to ntpd v4.2.8p4. To
see what ntpd version you are running, log into to your NTP server and
type ntpq and then rv. Also, monitor the system log for error messages
of the form "receive: Unexpected origin timestamp from %s", which could
indicate that you are subject to a priming-the-pump attack.
--- End Message ---
--- Begin Message ---
Hello,
thank you for spending your time helping to make Debian better with
this bug report. Unfortunately your bug report could not be (completely)
dealt with in an appropriate time.
The version you have filed this bug report against is for a release that
is not supported anymore. Unfortunately we do not have the manpower to
reproduce bugs that old. It is possibly already fixed with the current
version.
Therefor I'm closing this bug. If you can still reproduce this issue on
a supported release (Debian 9 aka stretch, preferably also in sid) feel
free to reopen the bug report.
Thanks,
Bernhard
--- End Message ---
