On Wed, 2019-10-16 at 14:19 +0200, Werner Koch wrote:
> On Tue, 15 Oct 2019 22:23, David Hebbeker said:
> > The manual [1] says that GnuPG can automatically retrieve keys for
> > emails in the "u...@example.com" form. Does this exclude emails
> > wrapped by angle brackets like "<u...@example.com>"?
> 
> That is fine.

Hi Werner and everyone,

thank you for your response, I was hoping that this would be possible. 

On the other hand, I have experienced a behavior I could only explain
with auto-key-locate being restricted to the pure form. Maybe you can
enlighten me on this case.

I demonstrate this behavior on a system which uses the attached
configuration file gpg.conf. I tested this with GnuPG 2.1.18 and
2.2.12. 

Preparation
===========
rm msg.*
echo "hello world" > msg.txt
gpg --batch --yes --delete-keys edward...@fsf.org

Bad Case (does not work)
========================
gpg --always-trust -e -r "<edward...@fsf.org>" msg.txt

        gpg: <edward...@fsf.org>: skipped: No public key
        gpg: msg.txt: encryption failed: No public key

Good Case (works)
=================
gpg --always-trust -e -r "edward...@fsf.org" msg.txt

        gpg: key 9FF2194CC09A61E8: 7454 signatures not checked due to
missing keys
        gpg: key 9FF2194CC09A61E8: public key "Edward, the GPG Bot <edw
ard...@fsf.org>" imported
        gpg: no need for a trustdb check with 'always' trust model
        gpg: Total number processed: 1
        gpg:               imported: 1
        gpg: automatically retrieved 'edward...@fsf.org' via keyserver


Note: The only difference is the missing angle brackets.

Can you please explain the difference? That would be of great help!

Thanks
David
keyserver hkp://keyserver.ubuntu.com:80
# Used for encryption
auto-key-locate keyserver
# Used for verifying signatures
auto-key-retrieve

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Reply via email to