Re: pgp_autosign=ask-no
- To: mutt-users@xxxxxxxx
- Subject: Re: pgp_autosign=ask-no
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Tue, 2 Oct 2007 16:25:56 -0500
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date:from:to:subject:message-id:references:mime-version:content-type:in-reply-to; q=dns/txt; s=default; bh=f4BVtemVt+6jhsPP7/I+47B8qVM=; b=VBP+Crx8KKQPHP7gV22B9WmEq6qJvwUJDzNIIoEdFLYEZSqqp42mPBiFUhR5B4bOwh+Ry0srQ/hHYEwybL2t4hid8jCwkhpYLDmy8saTiKJKcY9usskoXfqudEivnGtLO5dQkCT+H5n2N/F7KiOyyCDqD5F9gXGTBwtZ+xK1dT4=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=Buvx4X48UbfFm5cR9M05pBdIFpjXSbtZdP4HRh4tR2xVg55Vw1TdEtHWqa+OKbawmz4TSH0iSQ4ESSeaXzBK9l8cnNNjHuc5O/YyKDNx/ehGXZbsoNwzoZSI5/oDHhAfjH709vuQOXgzpadZDu3M5trTtzGY+8GzZc+v9P0EpFY=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:User-Agent;
- In-reply-to: <20071002203343.GA16222@xxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- References: <20071002203343.GA16222@xxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.16 (2007-09-19)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, October 2 at 02:33 PM, quoth Joseph:
>I was trying to assign value "ask-no" to pgp_autosign= but it doesn't work.
You mean crypt_autosign (pgp_autosign is a deprecated synonym for
crypt_autosign)? Yup; the documentation says it's just a boolean, not
a quad-option.
>Do I need to create macro if I want to selectively sign/encrypt emails?
No. For one thing, you can specify whether you want to encrypt/sign
mails on the compose menu just before sending the message. (press 'p')
It doesn't explicitly ask you, but just two keystrokes ('ps') toggles
signing, so it's only an extra keystroke over an ask-no answer to
pgp_autosign.
If it's always the same people, you can also set up send-hooks. I use
the groups feature to do this, so my send-hooks are really simple:
send-hook . 'unset crypt_autosign'
send-hook '%C pgp' 'set crypt_autosign'
Then all I need to do is tag my recipients, e.g.:
alias foo -group pgp Foo B. Baz <foo.b.baz@xxxxxxxxxxx>
And then all my emails to foo are signed. You can even get fancier:
send-hook . 'set crypt_autoencrypt=no'
send-hook '!~G ^%C pgp' 'set crypt_autoencrypt=yes'
What that does is encrypts things when all the recipients are marked
as 'encryption-ready' in my aliases file.
>2.) What do you have folks in your .mailcap for gpg I can not seem to
>find good entry.
Nothing. Inline PGP signatures (or encrypted messages) are sent as
text/plain, so you'd have to get fancy in your mailcap, and PGP-MIME
isn't structured for easy mailcap use, because it uses two separate
MIME message components to form a single signed message block. This is
why pine has such trouble with it: it's only set up to work on single
MIME components at a time. What you want to do is have mutt handle it
for you.
>When a message arrives I want to verify signature and/or decrypt it.
set pgp_auto_decode in your muttrc, and it'll Just Work.
~Kyle
- --
In wine there is wisdom, in beer there is strength, in water there is
bacteria.
-- German proverb
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFHArdkBkIOoMqOI14RAqotAJsE5BY+Pcm5Hm455D1cLseH9iTxaQCcDEmr
4cX6wOiCNpz4SNNlGGk38ck=
=so5w
-----END PGP SIGNATURE-----