home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.org.eff.talk:7102 misc.int-property:1458 alt.suit.att-bsdi:624 comp.unix.bsd:8992
- Newsgroups: comp.org.eff.talk,misc.int-property,alt.suit.att-bsdi,comp.unix.bsd
- Path: sparky!uunet!news.centerline.com!noc.near.net!news.Brown.EDU!qt.cs.utexas.edu!cs.utexas.edu!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!ulysses!ulysses!smb
- From: smb@ulysses.att.com (Steven Bellovin)
- Subject: Re: RSA Patent Abuse
- Message-ID: <1992Nov17.140200.130@ulysses.att.com>
- Date: Tue, 17 Nov 1992 14:02:00 GMT
- Distribution: usa
- References: <1992Nov11.005634.4977@netcom.com> <1992Nov13.174149.24017@mdd.comm.mot.com> <1992Nov14.062548.7038@u.washington.edu> <id.3Z0V.D62@ferranti.com>
- Organization: AT&T Bell Laboratories
- Lines: 63
-
- In article <id.3Z0V.D62@ferranti.com>, peter@ferranti.com (peter da silva) writes:
- > In article <1992Nov14.062548.7038@u.washington.edu> tzs@carson.u.washington.edu (Tim Smith) writes:
- > > Historical question: when did interest in public key cryptography become
- > > widespread among computer users? I recall that there was a public key
- > > email system from AT&T on some early Unix release (32V, I think).
- >
- > As I recall, secretmail was a private-key system. I'll check in my 2BSD
- > manual when I get home.
- >
- > > Most people seemed to play with it a bit, and then go to regular email for
- > > pretty much everything.
- >
- > Yep, it was pretty annoying to use, as well as being no more secure than
- > ordinary mail since your key was only protected by the file system security
- > and your email was already protected that well.
-
- No on the first count, not really on the second (rather, no worse than
- PGP or PEM). And the knapsack algorithm has since been cracked.
- Here's what the man page says on 4.3bsd; it's identical to what's in my
- (hard-copy) V7 manual:
-
-
- XSEND(1) USER COMMANDS XSEND(1)
-
- NAME
- xsend, xget, enroll - secret mail
-
- SYNOPSIS
- xsend person
- xget
- enroll
-
- DESCRIPTION
- These commands implement a secure communication channel; it
- is like mail(1), but no one can read the messages except the
- intended recipient. The method embodies a public-key cryp-
- tosystem using knapsacks.
-
- To receive messages, use enroll; it asks you for a password
- that you must subsequently quote in order to receive secret
- mail.
-
- To receive secret mail, use xget. It asks for your pass-
- word, then gives you the messages.
-
- To send secret mail, use xsend in the same manner as the
- ordinary mail command. (However, it will accept only one
- target). A message announcing the receipt of secret mail is
- also sent by ordinary mail.
-
- FILES
- /usr/spool/secretmail/*.key: keys
- /usr/spool/secretmail/*.[0-9]: messages
-
- SEE ALSO
- mail (1)
-
- BUGS
- It should be integrated with ordinary mail. The announce-
- ment of secret mail makes traffic analysis possible.
-
- Homer-land April 29, 1985 1
-
-