5 ms·
NTP Patches Flaws That Enable DDoS
- jlgaddis 10y agoUnrelated to NTP, but I (network engineer at an ISP) have also recently observed a few DDoS attacks using the "rpcbind/portmapper" service being used for amplification as well. The first time I saw this was fairly recently but I've seen a few more instances since then, which may be an indication that this will become more widely used in the future. Ensure that you've disabled unnecessary services and put a (default deny) firewall in front of your servers, for fuck's sake!
- zyztem 10y agoOh, FFS! BCP38 is 16 year old today. Please ensure that packets with spoofed source can not leave your network.
- kkirsche 10y agoWhile possible for customer networks you cannot do this for transit as you don't know the source address.
- NickNameNick 10y agoyou can still drop packets with invalid sources - private address ranges. reserved addresses, etc
- dgemm 10y agoTell that to China. Reflection attacks are still alive and well.
- toast0 10y agoI've seen a fair amount of chargen attacks; it's exciting because for whatever reason, the response packets are very large, so they're getting fragmented, but many people are trying to fix their outgoing chargen mess, and the first fragment (the one with the UDP port number) never arrives at my servers.
- imglorp 10y agoIt's worth pointing out that the NTPsec project is working hard on reducing the attack surface of NTP classic. At some point there will be few or no reasons to run NTP. http://esr.ibiblio.org/?p=7167 http://esr.ibiblio.org/?p=7167 https://www.ntpsec.org https://www.ntpsec.org
- jlgaddis 10y agoPersonally, I'm looking forward to phk's Ntimed (currently funded by the Linux Foundation).
- RyJones 10y agoright now LF is funding three development efforts for NTP.
- technion 10y agoAre you sure the project is still active? The README talks about first releases happening "soonish", but it's been over a year since the repo saw any activity. https://github.com/bsdphk/Ntimed https://github.com/bsdphk/Ntimed
- dfc 10y agoPeople make a lot of complaints about esr. The one thing I always thought esr excelled at was english composition. After reading that post it seems his writing skills have deteriorated.
- PhantomGremlin 10y agoI'm happy with OpenBSD's ntpd. I'm on a home cablemodem connection. All internal NTP traffic is redirected to my OpenBSD firewall, which is a client of 6 different NTP servers (including time.apple.com and some from us.pool.ntp.org). Right now my firewall's offset to the 6 servers is in the range of -6 ms to +8 ms. The delay to them varies between 26 ms and 95 ms. All in all, works great for me, and for many other people. And with a much lower attack surface than the reference NTP implementation. It's good to have alternatives.
- Thaxll 10y agoIs it too costly to check the source IP of UDP packets exiting ISPs networks?
- DanielDent 10y agoBCP-38 solves some people's problems, but it also causes a lot of problems. Triangular routing is a use case which becomes lost. As does the the ability to easily set up certain kinds of peering/multihoming connectivity. The larger and more complex a network gets, the harder it can become to determine if a source IP is "correct".
- rmdoss 10y agoToo complex for most large networks with many peers and client BGP announcements.
- jauer 10y agoNot really... On the low end (small ISPs with zero or a handful of downstream ASes), people aren't aware or are too lazy to implement egress ACLs. Complicating this: A surprising number of small ISPs and telcos don't actually staff for internet routing skills (e.g. can work with BGP & have heard of a BCP). They'll bring on a consultant to "turn up my new circuit" and move on. If the first consultant sets up egress ACLs and they get a new netblock chances are the next consultant will just remove the ACL instead of updating it... Medium to large ISPs: IRRs are supposed to solve this but implementation is spotty / OMG scripting changes on routers / etc. http://www.irr.net/docs/list.html http://www.irr.net/docs/list.html High end: I've heard that some providers have so many customers landing on a given aggregation router that the ACLs from IRRs end up too large for the router. Cogent's approach is to require a LOA for the subnets that you are announcing and filter out everything else. This seems reasonable, though it gets annoying when you have a downstream AS that has downstream ASes (BUT that's fairly uncommon). I use egress ACLs that allow my RIR-issued and downstream customer blocs and drop everything else. I have a friend that runs a slightly larger ISP (5x more downstream ASes) that does automation with IRRs.
- kkirsche 10y agoYou can in customer networks but how is the source IP helpful on a transit network where you receive it from another ISP or transit provider?
- ryuuchin 10y agoI've been under the impression for a while now that unless you needed the super accurate timekeeping that ntpd provides (most don't) you're better off just using openntpd which should exist in most distro's repo's[1]. It's basically just "good enough" for everybody who doesn't need sub ms accurate time keeping. [1] https://packages.debian.org/sid/openntpd https://packages.debian.org/sid/openntpd
- igni 10y agoIt probably depends on your operating system (or configuration manager, ancient SOE, etc) defaults.
- beagle3 10y agoIf you do need sub-ms accurate time keeping, then "just" running ntpd is not enough. You need to have a low-jitter connection to at least one stratum 1 server (if you don't know you have one, you don't), or a local clock. Otherwise, ntp doesn't give you more precision over openntpd -- only faster convergence after you've lost contact with servers for a few days. If you don't know _exactly_ why you need ntpd, the default should be openntpd.
- jedisct1 10y agoChrony is a good alternative: https://chrony.tuxfamily.org/ https://chrony.tuxfamily.org/