Given the definition[1] of the echo protocol works on UDP you could potentially spoof the address to be coming from another echo server and have packets going back and forth indefiniately, correct?
Doesn't spoofing the IP portion of UDP require a compliant network provider? I thought most upstream links would look at a spoofed packet and say, "Hey... no."
Not that this makes it impossible, just more difficult.
Comments
Given the definition[1] of the echo protocol works on UDP you could potentially spoof the address to be coming from another echo server and have packets going back and forth indefiniately, correct?
https://tools.ietf.org/html/rfc862
This is the premise of an old bit of code called Pepsi.c. I recall having juvenile fun with it. Many Cisco routers at the time had these ports open. http://www.hoobie.net/security/exploits/hacking/pepsi.c
Source code written by teenagers is always such a joy.
Especially the greetz and rage. I knew quite a few on both sides 😂
Doesn't spoofing the IP portion of UDP require a compliant network provider? I thought most upstream links would look at a spoofed packet and say, "Hey... no."
Not that this makes it impossible, just more difficult.
Sounds like PingFS. https://github.com/yarrick/pingfs