From: <jari.aalto@poboxes.com>(+list.ding)
Subject: Re: Gnus PGP Questions
Date: 03 Apr 1998 11:44:38 +0300 [thread overview]
Message-ID: <tbn2e3l2fd.fsf@blue.sea.net> (raw)
In-Reply-To: Stainless Steel Rat's message of "02 Apr 1998 14:32:29 -0500"
[-- Attachment #1: Type: text/plain, Size: 2728 bytes --]
| 98-04-02 Stainless Steel Rat <ratinox@peorth.gweep.net> list.ding
|
| >>>>> "CS" == Christoph Seibert <seibert@cs.uni-bonn.de> writes:
| CS> <application/pgp-encrypted> - header) with Gnus.
|
| Hoo-boy.
|
| Both PGP/MIME and X-PGP have similar flaws: if the message body is altered
| by the inclusion or removal of whitespace, a transformation that many
| transfer agents will perform, it is impossible to properly reconstruct the
| message for validation or decryption.
Erm. I haven't encountered such MTA yet.
The PGP/MIME has worked fine. It's also standard.
| CS> When no matching key is found, it seems I can only try to "fetch" it. I
| CS> haven't found a way yet to enter an alternative key-ID by hand (as in
| CS> mc-encrypt).
|
| The PGP/MIME tools are woefully inadequate for any serious PGP user.
I have used PGP/MIME for 2 years now without problems in Emacs/TM.
| suggestion is to use mailcrypt instead. It works, it works as reliably as
| PGP itself. Any good MUA that groks PGP will (or at least can) hide PGP's
| delimiter lines and signature blocks.
| [Christoper continues]
|
|1) When I do mime-editor/set-encrypt and try to send the message, the
|complete "To:" address is used to find the key...
| So when someone has a new mail address or
|there's a slight change in the user ID, I can't send him a
|PGP-encrypted message without him adding the new ID to his key and me
|adding this key to my public keyring. This is very annoying. :-(
TinyPgp can handle this. you just define REGEXP to match
emails and specify keyHexId or email address where to translate the
See section 12.7 from the manual.
ftp://cs.uta.fi/pub/ssjaaa/ema-tipgp.html
|2) How can I send messages "Sign & Encrypt"? mime-editor/set-encrypt
TinyPgp has this "one pass, Sign & Encrypt" command: C-c / t
|signed and encrypted - only not following PGP-Elkins, but PGP-Kazu.
But for MIME you don't have to call it yourself.
|How can I (without calling "only" mc-decrypt)
|
|1) reply to PGP-encrypted messages so that the decrypted message gets
|quoted?
Good suggestion. I haven't thought this yet. Will be
corrected in next release.
|2) optionally (or always) replace the en- by the decrypted message on
|disk as in mc-decrypt?
Replacing MIM/PGP message is a bit hairy, because TM takes the
control. But I check if I have add this feature to TinyPgp too.
|3) decrypt and display a PGP-encrypted message by pressing a key in
|the Summary buffer or automagically by using an appropriate hook
|without having to use the mouse? That is, how can I simulate mouse-2
|on the appropriate MIME-header?
TinyPgp has Summary-minor mode, but I don't it doesn't know MIMe/PGP
yet, only regular PGP. I'll add this feature to todo.
jari
[-- Attachment #2: Type: application/pgp-signature, Size: 244 bytes --]
prev parent reply other threads:[~1998-04-03 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-02 11:22 Christoph Seibert
[not found] ` <x7vhss81f6.fsf@peorth.gweep.net>
1998-04-03 8:44 ` +list.ding [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tbn2e3l2fd.fsf@blue.sea.net \
--to=jari.aalto@poboxes.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).