Your message dated Wed, 13 Sep 2006 13:08:00 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#155933: ntpdate: debug and simple query should not force
unprivileged port
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: ntpdate
Version: 1:4.1.0-8
Severity: normal
IMHO, in line 1571 in ntp-4.1.0/ntpdate/ntpdate.c binding to the
unprivileged port should only be determined by unpriv_port --- it is
perfectly legitimate to do a -d or -q query from the ntp port. If an
unprivileged port is desired, one can always use the -u flag.
I get bitten by this because adjtimex --log calls ntpdate with the -d
flag and my firewall insists on outgoing NTP connections originating
at the NTP port.
Thanks,
Hein
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux qaip3 2.4.18qaip3-5 #1 Mon Mar 25 09:35:57 CET 2002 i686
unknown unknown GNU/Linux
Versions of the packages ntpdate depends on:
ii debconf 1.1.22 Debian configuration management system
ii libc6 2.2.5-13 GNU C Library: Shared libraries and Timezone
ii libreadline4 4.3-4 GNU readline and history libraries, run-time
--- Begin /etc/init.d/ntpdate (modified conffile)
#! /bin/sh
test -f /usr/sbin/ntpdate || exit 0
. /etc/default/ntp-servers
test -n "$NTPSERVERS" || exit 0
case "$1" in
start|restart|force-reload)
echo -n "Running ntpdate to synchronize clock"
/usr/sbin/ntpdate -b -s $NTPSERVERS
echo "."
;;
stop)
;;
*)
echo "Usage: /etc/init.d/ntpdate {start|stop|restart|force-reload}"
exit 1
esac
exit 0
--- End /etc/init.d/ntpdate
--- End Message ---
--- Begin Message ---
I don't see a bug here. The behavior is documented and uncontested
rationale has been given.
--- End Message ---
