Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by michaelmior on Thursday February 13, 2014 @10:04AM
(#7231696)
As far as I can tell, the default Ubuntu ntpd config still allows monlist. (That is, /etc/ntp.conf in saucy doesn't have disable monitor.)
[ Parent
| on HN ]
Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by makomk on Thursday February 13, 2014 @11:44AM
(#7232321)
The Debian default config has noquery set for everywhere but localhost which is I believe safer (disables all ntpdc queries not just the one used here). Ubuntu's likely the same.
Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by michaelmior on Thursday February 13, 2014 @12:05PM
(#7232483)
The default Ubuntu config has the following
restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery
Edit: Note that this also exists in Ubuntu 12.04, so the latest LTS is fine as well.
Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by michaelmior on Thursday February 13, 2014 @11:49AM
(#7232360)
Yes, noquery is enabled (at least in saucy). It isn't however in precise, which is the current LTS. I'm unclear of the difference between noquery and disable monitor.
Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by devicenull on Thursday February 13, 2014 @11:19AM
(#7232150)
disable monitor is not really the best way to fix this. You're better off adding 'noquery' to the end of the 'restrict default' lines.
Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by michaelmior on Thursday February 13, 2014 @11:49AM
(#7232364)
Thanks for clarifying. I'm not familiar with ntpd configuration as it's something I usually just install and forget about.