Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by Karunamon on Thursday February 13, 2014 @11:19AM
(#7232147)
>It just gives up that data to anyone that asks? Seems like a huge privacy issue.
I could do a nmap on the public internet and probably get a similar amount of addresses. An IP is about as "private information" as a phone number nowadays (You know, those things that get sent out en masse in yellow and white books for public consumption with real-life names next to them).
Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by buzzkills on Thursday February 13, 2014 @10:06AM
(#7231703)
What like this one? https://www.apache.org/server-status
Re:Technical Details Behind a 400Gbps NTP Amplification DDoS...
by devicenull on Thursday February 13, 2014 @01:22PM
(#7233055)
Huh? Those are completely different issues.
So you synced your time with a server. Why would anyone else care about that? Why does it matter if someone else knows you're syncing time?
This is a very different service then a web browser.
It just gives up that data to anyone that asks? Seems like a huge privacy issue.
Imaging Apache or Nginx giving up the last 600 IPs it served and maybe the URLs they went to.
edit: there is always the occasionally open Apache /server-status handler that leaks this type of data.