3 ms·
Reminds me of the '90s when WinNuke and Smurf attacks ran wild. Remember one attack that caused our Linux boxes to panic, but I can't remember what it was calle
by pixl97 14y ago
Reminds me of the '90s when WinNuke and Smurf attacks ran wild. Remember one attack that caused our Linux boxes to panic, but I can't remember what it was called. It's not surprising that we're seeing stuff like this in v6. IPv4 has had the bugs hammered out from years of attacks, v6 not so much.
- dfc 14y agoPing of Death: http://insecure.org/sploits/ping-o-death.html http://insecure.org/sploits/ping-o-death.html
- metalruler 14y agoLand? A single spoofed TCP SYN packet with identical src/dst addresses was enough to crash or at least impact many OSs. http://www.physnet.uni-hamburg.de/physnet/security/vulnerability/land.html http://www.physnet.uni-hamburg.de/physnet/security/vulnerabi...
- sargun 14y agoExcept, for this attack you have to be link-local (fe80 is local scope, and so are router advertisements). Realistically, for most server installs you're okay. For coffee shops with an open, insecure broadcast domain, not so much
- alexkus 14y ago> Remember one attack that caused our Linux boxes to panic, but I can't remember what it was called. teardrop?
- highwind 14y agoDoes anyone know how long it took for operating systems to implement ipv4 in a secure and stable manner?