Evil bit (nonfiction): Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
The '''evil bit''' is a [[Fiction (nonfiction)|fictional]] IPv4 packet header field proposed in RFC 3514, a humorous April Fools' Day RFC from 2003 authored by Steve Bellovin. | The '''evil bit''' is a [[Fiction (nonfiction)|fictional]] IPv4 packet header field proposed in RFC 3514, a humorous April Fools' Day RFC from 2003 authored by Steve Bellovin. | ||
The RFC recommended that the last remaining unused bit in the IPv4 packet header be used to indicate whether a packet had been sent with | The RFC recommended that the last remaining unused bit 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. | ||
== In the News == | == In the News == | ||
Revision as of 15:40, 26 July 2016
The evil bit is a fictional IPv4 packet header field proposed in RFC 3514, a humorous April Fools' Day RFC from 2003 authored by Steve Bellovin.
The RFC recommended that the last remaining unused bit 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.
In the News
This photograph, if genuine, may show the moment following the release of an evil bit by supervillain Fugitive Rubies.
Fiction cross-reference
- Carnevale Tenebre
- Evil bit release
- Gnomon Algorithm
- Hollerith
- Killer Poke - software defect and contract killer for hire.
- Malvoleum - an evil grease derived from Sweet, sweet crude oil.
- Murder, Incorporated 1.1
- One If By Good, Zero If By Evil
- Ticketology
Nonfiction cross-reference
External links:
- Evil bit @ Wikipedia