From: Kevin Brubeck Unhammer <unhammer@fsfe.org>
To: info-gnus-english@gnu.org
Subject: Re: How to set up signing/encryption with GnuPG? Some newbie questions
Date: Tue, 16 Oct 2012 21:45:20 +0200 [thread overview]
Message-ID: <87pq4inqun.fsf@fsfe.org> (raw)
In-Reply-To: <58e2ae8a-d659-4960-9c43-ccfcd6001efb@googlegroups.com>
Marius Hofert <marius.hofert@math.ethz.ch> writes:
>> > 1) What is a useful/meaningful setup in ~/.gnus.el for obtaining enabling GnusPG
>> > for PGP/MIME?
>> > I figured the following to be useful:
>> > (setq mm-verify-option 'always); always verify signed parts
>> > (setq mm-decrypt-option 'always); always decrypt encrypted parts
>> > (setq gnus-message-replysign t); gnus-message-replyencrypt,
>> > gnus-message-replysignencrypted are already t by default
>> > I also found Gnus users who set
>> > (setq gnus-treat-x-pgp-sig t)
>> > but I could not find sufficient documentation of gnus-treat-x-pgp-sig to
>> > determine whether this is useful.
>>
>> There's also these two (defaulting to nil):
>>
>> mm-sign-option 'guided
>> mm-encrypt-option 'guided
>
> Thanks, Kevin.
>
> Do you know what gnus-treat-x-pgp-sig does? I could not find documentation on this.
`C-h v gnus-treat-x-pgp-sig RET' lead me to the info files, whence I
found this:
`W p'
Verify a signed control message (`gnus-article-verify-x-pgp-sig').
Control messages such as `newgroup' and `checkgroups' are usually
signed by the hierarchy maintainer. You need to add the PGP
public key of the maintainer to your keyring to verify the
message.(1)
--
Kevin Brubeck Unhammer
GPG: 0x766AC60C
prev parent reply other threads:[~2012-10-16 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 7:41 Marius Hofert
2012-10-16 9:21 ` Kevin Brubeck Unhammer
2014-05-15 19:40 ` Peter Münster
[not found] ` <mailman.11101.1350379384.855.info-gnus-english@gnu.org>
2012-10-16 14:42 ` Marius Hofert
2012-10-16 19:45 ` Kevin Brubeck Unhammer [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=87pq4inqun.fsf@fsfe.org \
--to=unhammer@fsfe.org \
--cc=info-gnus-english@gnu.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).