From: Luke Yelavich <themuso@themuso.com>
To: speakup@braille.uwo.ca
Subject: Re: Auto-verification of pgp/inline messages not working
Date: Tue, 24 Jan 2006 13:49:27 +1100 [thread overview]
Message-ID: <20060124024927.GA7307@localhost.localdomain> (raw)
In-Reply-To: <20060123231208.GA5117@garrettk17.iquest.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Jan 24, 2006 at 10:12:08AM EST, Garrett Klein wrote:
> Hello all,
>
> About a week and a half ago mutt stopped automagically verifying pgp signatures created as pgp/inline (i.e. what everyone uses on this list). The last thing I remember before it stopped working that would be significant is being prompted for a passphrase, couldn't tell you what in the world for... but anyway now I have to press escape and then uppercase p on a traditional pgp-signed message. Any ideas as to why this might be happening? BTW Igor and I did some tests and I can verify both attached and detached signatures from him.
I have been experiencing the same thing. More to the point, it has been
happening on other lists that I am on where people are using inline
signatures. Attached signatures are having no problem being picked up.
My GPG related mutt configuration has not changed at all since I set up
my muttrc file, and GPG keys, etc.
- --
Luke Yelavich
GPG key: 0xD06320CE
(http://www.themuso.com/themuso-gpg-key.txt)
Email & MSN: themuso@themuso.com
ICQ: 18444344
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFD1ZW3jVefwtBjIM4RAr+4AJ0W3g1UXYyqVBeWqq2M22F8brVx3QCg4df3
pp2VGUQ7DiO+G6aHFk1SZWY=
=V/ya
-----END PGP SIGNATURE-----
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Garrett Klein
` Luke Yelavich [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=20060124024927.GA7307@localhost.localdomain \
--to=themuso@themuso.com \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).