Evil Bit Added to TCP/IP Packets
Absolut Ralts notes that "
RFC 3514 is now
available. It provides for an additional so called 'Evil Bit' that can be
used to determine the nature of the TCP/IP packet. This should vastly simplify networking and internet security, and prevent the beepers of tired sysadmins from going off and interfering with Warcraft III!"
Or is this just a cruel Slashdot April Fool's prank?
:)
Oh, and first (subjectively, anyway) post!
Editor Emeritus and Senior Writer, TeleRead.org
It looks like I was correct in suspecting /. changing thier firewall ruleset to allow packets with the evil bit enabled first. Normal packets are trottled down to a crwal. It took me only a few minutes to change the tcpip stack so I can read /. again at decent speeds :)
I sniffed the packets from this duplicate article, and the evil bit was not set! I demand Slashdot immediately implement RFC3514 for all duplicate articles!
--
"Open source is good." - Steve Jobs
"Open source is evil." - Microsoft
What's the point of having an evil bit if you don't do something evil with it time and again. I mean, it IS an evil bit after all, what do you expect. It's not every person who knows how to make the most of an evil bit. It's not like it's an evil byte you know, but one of those could come in handy, it's an evil bit, and you simply have to make the most of an evil bit, because it's only so much evil, hardly enough to go around, don't you know.