Page 1 of 1

NTP Problem

PostPosted: Thu Sep 19, 2013 8:12 am
by mohs3n
Hi

I have successfully patched vanila kernel "3.2.51" with "grsecurity-2.9.1-3.2.51-201309162119" on Debian Wheezy and everything works fine except ntp .
I get this error when i run 'ntpq -p' :
Code: Select all
localhost: timed out, nothing received
***Request timed out


Grsecurity log :
Code: Select all
Sep 19 16:31:44 cloud-test kernel: [    4.610197] grsec: time set by /sbin/hwclock[hwclock:531] uid/euid:0/0 gid/egid:0/0, parent /lib/udev/hwclock-set[hwclock-set:520] uid/euid:0/0 gid/egid:0/0
Sep 19 16:32:00 cloud-test kernel: [   24.314873] grsec: time set by /usr/sbin/ntpd[ntpd:2228] uid/euid:102/102 gid/egid:104/104, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0


Note : RBAC is disabled.
Any suggestion would be appreciated.

Re: NTP Problem

PostPosted: Thu Oct 03, 2013 4:34 pm
by ldunston
[quote][/quote]

Can you post the contents of /etc/ntp.conf?

You say this happens with RBAC disabled?

Have you tried running strace on the ntp process?

Re: NTP Problem

PostPosted: Wed Oct 09, 2013 4:22 am
by mohs3n
Sorry for the delay .
I removed/purged ntp from server and reinstall it and it worked!
Im not sure why but i can query the ntp now
Code: Select all
# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+helium.constant 96.47.67.105     2 u   15   64    1   70.057   -0.269   0.245
-2.ntp.tld.sk    161.143.24.141   2 u   12   64    1  169.717   -3.983   3.707
+ntp3.Housing.Be 128.32.206.55    2 u   13   64    1   11.463    0.843   0.210
*hydrogen.consta 209.51.161.238   2 u   10   64    1   66.654   -1.393   0.252

Re: NTP Problem

PostPosted: Tue Oct 29, 2013 4:14 pm
by sfs6dzs
I guess initially (I don't have experience with RBAC at all but what I read from spender's slides) Network traffic is allowed so you shouldn't have any issues, although you may want to limit it to what's needed if possible, I may be wrong however, and if so, please correct me.