home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky sci.crypt:7127 alt.security.pgp:597
- Path: sparky!uunet!spool.mu.edu!yale.edu!ira.uka.de!smurf.sub.org!news
- From: urlichs@smurf.sub.org (Matthias Urlichs)
- Newsgroups: sci.crypt,alt.security.pgp
- Subject: Re: PGP messages readable by more than one person
- Date: 25 Jan 1993 10:51:32 +0100
- Organization: University of Karlsruhe, FRG
- Lines: 33
- Message-ID: <1k0d74$92c@smurf.sub.org>
- References: <1993Jan23.192239.14870@infodev.cam.ac.uk> <WARLORD.93Jan24213831@snorkelwacker.mit.edu>
- NNTP-Posting-Host: 127.0.0.1
-
- In alt.security.pgp, article <WARLORD.93Jan24213831@snorkelwacker.mit.edu>,
- warlord@MIT.EDU (Derek Atkins) writes:
- >
- > PGP 2.2 *WILL* have multiple-recipient encryption! The code is done.
- > The patches are in. All that's needed is a 2.2 release to happen!
- >
- While we're on the subject of new releases..:
- - Nonblocking I/O is not undone when an interrupt signal is received.
- - No gratuitious appending of suffixes for command-line arguments please.
- UNIX isn't DOS.
- - Make pgp -kxaf work. Ditto pgp -kaf.
- - When extracting a key, I'd like to select which certifications for
- that key get exported.
- - How do I get pgp -fst/-fsat to not encode the message I want to sign?
- - Thoughts about better MIME integration? The MIME multipart stuff
- would be a far better idea than these BEGIN PGP lines.
- Define an "application/pgp" subtype ?
-
- --
- No matter how subtle the wizard, a knife in the shoulder blades will
- seriously cramp his style.
- --
- -----BEGIN PGP PUBLIC KEY BLOCK-----
- Version: 2.1
-
- mQBYAitirlIAAAECWLA75SRTAZb8WsAB4kJCAmxM4h01UgErYLqOCOolntDCA502
- Zr6rqV39QKwx6tton9AtTgPKrfdz6ufnAL9E45BJgO4zcJBNac3pMwAFEbQoTWF0
- dGhpYXMgVXJsaWNocyA8dXJsaWNoc0BzbXVyZi5zdWIub3JnPg==
- =FMCO
- -----END PGP PUBLIC KEY BLOCK-----
- --
- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\
- Humboldtstrasse 7 -- 7500 Karlsruhe 1 -- Germany -- +49-721-9612521 \o)/
-