From: Turbo Fredriksson <turbo@tripnet.se>
Cc: ding@gnus.org
Subject: Re: Verifying signatures with Mailcrypt
Date: 01 Dec 1999 11:29:08 +0100 [thread overview]
Message-ID: <7bpuwrc5u3.fsf@junk.nocrew.org> (raw)
In-Reply-To: David Porter's message of "Tue, 30 Nov 1999 09:11:04 +1100"
>>>>> "David" == David Porter <dporter@turing.une.edu.au> writes:
David> On Mon, 29 Nov, 1999 at 07:08:34pm +0000, Graham Murray
David> wrote:
>> Karl Kleinpaste <karl@justresearch.com> writes:
>>
>> > Have you specified... > (add-hook 'gnus-summary-mode-hook
>> 'mc-install-read-mode) > ...in .gnus?
>>
>> That will not help. Currently mailcrypt, using C-c / v will
>> verify signatures which (like in this one) are part of the
>> message. It will *not* work for separate mime signatures.
David> So how are mailcrypt users verifying separate mime
David> signatures? Saving the parts to file and running GPG
David> manually or something?
I once wrote some own functions that did this. It may not be pretty, but
it works... Have a look at http://www.nocrew.org/~turbo/pgp-mime.el
There's much more crap in there to, but you'll get the point :)
--
--
Noriega Clinton BATF SDI munitions AK-47 supercomputer $400 million in
gold bullion Honduras quiche kibo Peking Legion of Doom nuclear Mossad
prev parent reply other threads:[~1999-12-01 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-29 11:15 David Porter
1999-11-29 16:20 ` Karl Kleinpaste
1999-11-29 19:08 ` Graham Murray
1999-11-29 22:11 ` David Porter
1999-11-29 22:56 ` Brian May
1999-11-29 23:20 ` David Porter
1999-11-30 0:20 ` S/MIME (was Re: Verifying signatures with Mailcrypt) Bruce Stephens
1999-11-29 22:56 ` Verifying signatures with Mailcrypt Hal Snyder
1999-12-01 10:29 ` Turbo Fredriksson [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=7bpuwrc5u3.fsf@junk.nocrew.org \
--to=turbo@tripnet.se \
--cc=ding@gnus.org \
/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).