This article may rely excessively on sources too closely associated with the subject, potentially preventing the article from being verifiable and neutral. (August 2015) |
The evil bit is a fictional IPv4 packet header field proposed in a humorous April Fools' Day RFC from 2003,[1] authored by Steve Bellovin. The Request for Comments recommended that the last remaining unused bit, the "Reserved Bit"[2] in the IPv4 packet header, be used to indicate whether a packet had been sent with malicious intent, thus making computer security engineering an easy problem – simply ignore any messages with the evil bit set and trust the rest.
Impact
editA 2015 research done by network engineer Ben Cartwright-Cox revealed that a number of popular websites (436 websites out of Alexa 20k at the time), such as those belonging to several universities and banks, to antivirus provider Kaspersky and to remote desktop software provider Teamviewer respect the "evil bit" by dropping the inbound request, making them compliant with RFC 3514.[3]
Influence
editThe evil bit has become a synonym for all attempts to seek simple technical solutions for difficult human social problems which require the willing participation of malicious actors, in particular efforts to implement Internet censorship using simple technical solutions.
As a joke, FreeBSD implemented support for the evil bit that day, but removed the changes the next day.[4] A Linux patch implementing the iptables module "ipt_evil" was posted the next year.[5] Furthermore, a patch for FreeBSD 7 is available,[6] and is kept up-to-date.
There is an extension for XMPP protocol, inspired by evil bit.[7]
This RFC has also been quoted in the otherwise completely serious RFC 3675, ".sex Considered Dangerous", which may have caused the proponents of .xxx to wonder whether the Internet Engineering Task Force (IETF) was commenting on their application for a top-level domain (TLD) – the document was not related to their application.[8]
For April Fool's 2010, Google added an &evil=true parameter to requests through the Ajax APIs.[9]
A patch to add compatibility for RFC 3514 in Wireshark was proposed but never implemented.[10]
See also
editReferences
edit- ^ S. Bellovin (April 1, 2003). The Security Flag in the IPv4 Header. Network Working Group. doi:10.17487/RFC3514. RFC 3514. Informational. This is an April Fools' Day Request for Comments.
- ^ Rocha, Luis (April 1, 2013). "The Evil Bit". Count Upon Security. Retrieved May 9, 2016.
- ^ "I may be the only evil (bit) user on the internet". blog.benjojo.co.uk. Retrieved September 13, 2024.
- ^ Implementation, removal
- ^ "ipt_evil, kernel part". Archived from the original on February 2, 2011. Retrieved January 1, 2011.
- ^ "RFC3514 for FreeBSD7". Archived from the original on February 18, 2009. Retrieved December 26, 2013.
- ^ Saint-Andre, Peter; Hildebrand, Joe (April 1, 2003). "XEP-0076: Malicious Stanzas". Archived from the original on April 16, 2013.
- ^ "Adult-Related TLDs Considered Dangerous". Retrieved July 6, 2017.
- ^ "Helping you help us help you". googleajaxsearchapi.blogspot.co.uk. Retrieved February 19, 2017.
- ^ "Wireshark · Ethereal-dev: [Ethereal-dev] Patch: RFC 3514 support". Wireshark. Retrieved May 15, 2024.