Gnus development mailing list
 help / color / mirror / Atom feed
From: Graeme Mathieson <mathie@wossname.org.uk>
Subject: PGG signature verification
Date: Sun, 06 Apr 2003 07:23:36 +0100	[thread overview]
Message-ID: <sa61y0gm9ef.fsf@kerouac.projectcolo.org.uk> (raw)


I think I've managed to setup PGG to automatically verify PGP signatures
(it's mostly PGP/MIME I'm interested in, having recently switched from
Mutt), with some of the following configuration:

,----
| (require 'pgg)
| (setq pgg-default-scheme 'gpg)
| (setq mml-signencrypt-style-alist '(("pgpmime" combined)
|                                     ("pgp" combined)
|                                     ("smime" combined)))
| (setq mm-verify-option 'known
|       mm-decrypt-option 'known
|       gnus-message-replysign t
|       gnus-message-replyencrypt t
|       mml-default-sign-method "pgpmime"
|       mml-default-encrypt-method "pgpmime")
`----

(The mml-default-(sign|encrypt)-method part took a while to find; that
defaults to signing with PGP/MIME instead of S/MIME.)

This all works nicely.  There's one thing I'm not clear on, though.  How
does Gnus indicate to me that a signature has successfully been verified
(with mm-verify-option)?  I can see that it's doing *something* to
verify signed messages since it can take longer to display them, but
there's no apparent indication that the verification was successful.

-- 
Right now, there are scr1pt k1dd13s plotting to DDoS my network, my co-lo
server is not responding  to pings and  the people that I IRC with may be
involved in both.  I'm  sysadmin Graeme Mathieson and this is the longest
day of my life.                               http://www.wossname.org.uk/




             reply	other threads:[~2003-04-06  6:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06  6:23 Graeme Mathieson [this message]
2003-04-06 13:11 ` Daniel Pittman
2003-04-06 13:24 ` Jesper Harder

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=sa61y0gm9ef.fsf@kerouac.projectcolo.org.uk \
    --to=mathie@wossname.org.uk \
    /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).