d_anderson writes: > Thanks! I quickly skimmed through the document, and I think I am > asking the wrong questions..
I've been trying to think of good reasons to authenticate pool servers and I haven't come up with any good ones yet. > Assuming again a single client, syncing from a public NTP pool, are > there any glaring security issues that have to be addressed (apart > from sane configuration parameters like "nomodify nopeer noquery > notrap" and "restrict"-s)? I read somewhere that usually clients don't > need to be concerned but I just want to make sure.. If the ntpd instance is visible on the public internet then you need to secure it. If you need accurate time and want to use the pool, use the pool directive. If you want to have fallback assurances and don't have lots of $, get a decent GPS puck. They can be had for under US$40. H _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions