home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: sci.crypt
- Path: sparky!uunet!telebit!phr
- From: phr@telebit.com (Paul Rubin)
- Subject: Re: Disclosing a new encryption method (the other side)
- In-Reply-To: butzerd@columbia.eng.ohio-state.edu's message of Wed, 11 Nov 1992 18:29:02 GMT
- Message-ID: <PHR.92Nov11195700@napa.telebit.com>
- Sender: news@telebit.com
- Nntp-Posting-Host: napa.telebit.com
- Organization: Telebit Corporation; Sunnyvale, CA, USA
- References: <1992Nov11.182902.29740@ee.eng.ohio-state.edu>
- Date: 11 Nov 92 19:57:00
- Lines: 20
-
- For a crypto system to be competetive nowadays, it must withstand the
- same kinds of attacks that existing systems have proven their ability
- to withstand. This means all the methods that cryptography users,
- including industrial, military, and criminal [ :-) ] organizations are
- able to muster---including not just cryptanalysis, but commando raids
- on traffic endpoints, plus the use of bribery, seduction, and torture
- to get the algorithms and other info out of people. You have to
- assume that both the algorithm and an unlimited amount of encrypted
- traffic with known plaintext and known keys are available to the
- enemy. They WILL get this info. You can then change the keys,
- but once they know the algorithm you can never make them stop knowing it.
- Your system (with the new keys) must continue to withstand cryptanalysis.
- The existing ones do---if yours doesn't, you don't have a worthwhile method.
-
- THAT is why you have to publish your algorithm (or post permission the
- sci.crypt commando squads to break into your home) if you want anyone
- to take you seriously when you say it is secure.
-
- For relevant war stories, see "The Codebreakers" by David Kahn.
-
-