From: Daniel Patterson <dbp@dbpmail.net>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: Emacs not finding keys to verify signatures
Date: Fri, 28 Jun 2013 09:11:54 -0400 [thread overview]
Message-ID: <87ehbmpeg5.fsf@mbp.dbpmail.net> (raw)
In-Reply-To: <87sj028ovv.fsf@zancas.localnet>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
David Bremner <david@tethera.net> writes:
>> I click on it, and it requests _my_ public key from the key server, and
>> of course nothing changes - because I already had the key.
>
> So after you click, the key downloads, and the button does not change
> colour?
Yes. After it downloads, it still says "Unknown key KEYID or unsupported
algorithm". I would be confused by the unsupported algorithm - it is
just an RSA/RSA key, newly created. This has also happened for other
signed messages - it downloads the key, but still says it doesn't know
the key (and this persists across restarts of emacs).
>> Any ideas? Is this because of some missing package or misconfigured
>> setting? I'm using the latest released version of notmuch (0.15.2),
>> emacs 24.2.1, and gpg 1.4.11.
>
> Does using easypg from within emacs work for you? You can try with
> "M-x epa-list-keys"
That works, and it shows the key there.
One thing I forgot to mention - I have notmuch running on a remote
server through ssh. I don't really imagine this would be an issue, but
maybe? (I also have the library installed locally, for emacs).
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2013-06-28 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 14:59 Emacs not finding keys to verify signatures Daniel Patterson
2013-06-28 11:18 ` David Bremner
2013-06-28 13:11 ` Daniel Patterson [this message]
2013-06-28 15:05 ` David Bremner
2013-06-28 15:13 ` Daniel Kahn Gillmor
2013-06-29 15:24 ` Daniel Patterson
2013-06-30 20:05 ` Daniel Kahn Gillmor
2013-06-30 20:13 ` Daniel Patterson
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ehbmpeg5.fsf@mbp.dbpmail.net \
--to=dbp@dbpmail.net \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).