Chinese Lottery Cryptanalysis Revisited: The Internet as a Codebreaking Tool
draft-leech-chinese-lottery-04
This document is an Internet-Draft (I-D) that has been submitted to the Independent Submission stream.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
The information below is for an old version of the document that is already published as an RFC.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 3607.
|
|
---|---|---|---|
Author | Marcus D. Leech | ||
Last updated | 2015-10-14 (Latest revision 2003-02-13) | ||
RFC stream | Independent Submission | ||
Intended RFC status | Informational | ||
Formats | |||
Stream | ISE state | (None) | |
Consensus boilerplate | Unknown | ||
Document shepherd | (None) | ||
IESG | IESG state | Became RFC 3607 (Informational) | |
Action Holders |
(None)
|
||
Telechat date | (None) | ||
Responsible AD | Steven M. Bellovin | ||
Send notices to | (None) |
draft-leech-chinese-lottery-04
A new Request for Comments is now available in online RFC libraries. RFC 3607 Title: Chinese Lottery Cryptanalysis Revisited: The Internet as a Codebreaking Tool Author(s): M. Leech Status: Informational Date: September 2003 Mailbox: mleech@nortelnetworks.com Pages: 8 Characters: 14526 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-leech-chinese-lottery-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3607.txt This document revisits the so-called Chinese Lottery massively-parallel cryptanalytic attack. It explores Internet-based analogues to the Chinese Lottery, and their potentially-serious consequences. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.