Re: are angle brackets around email address allowed for auto-key-locate?
On Tue 2019-10-22 06:48:44 +0200, David Hebbeker wrote: > On Wed, 2019-10-16 at 20:26 +0200, David Hebbeker wrote: >> 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 ""? >> > >> > That is fine. >> >> I have experienced a behavior I could only explain with auto-key- >> locate being restricted to the pure form. > > I still have the problem described in my previous e-mail. Can it be > that this is faulty behavior of the GnuPG? Yes, i can confirm the same misbehavior with GnuPG 2.2.17 (though i don't think that edward...@fsf.org is actually correctly published via WKD, so i tested with d...@fifthhorseman.net): 130 dkg@alice:/tmp/cdtemp.pipIPp$ gpg -e -r '' foo.txt gpg: : skipped: No public key gpg: foo.txt: encryption failed: No public key 2 dkg@alice:/tmp/cdtemp.pipIPp$ gpg -e -r 'd...@fifthhorseman.net' foo.txt gpg: removing stale lockfile (created by 29177) gpg: key F20691179038E5C6: "Daniel Kahn Gillmor " 1 new user ID gpg: key F20691179038E5C6: "Daniel Kahn Gillmor " 8 new signatures gpg: Total number processed: 1 gpg: new user IDs: 1 gpg: new signatures: 8 gpg: no ultimately trusted keys found gpg: B0A9B7B2D8D2CE47: There is no assurance this key belongs to the named user sub cv25519/B0A9B7B2D8D2CE47 2019-01-19 Daniel Kahn Gillmor Primary key fingerprint: C4BC 2DDB 38CC E964 85EB E9C2 F206 9117 9038 E5C6 Subkey fingerprint: 88DE 0083 5288 C784 E73A C940 B0A9 B7B2 D8D2 CE47 It is NOT certain that the key belongs to the person named in the user ID. If you *really* know what you are doing, you may answer the next question with yes. Use this key anyway? (y/N) y 0 dkg@alice:/tmp/cdtemp.pipIPp$ > I would create a bug report at [1] so it does not get lost. Does > something speak against it? Yes, in the future, please report this sort of bug directly so that we can track the problem. i've opened https://dev.gnupg.org/T4726 now -- please add any additional information there! Thanks for the report, --dkg signature.asc Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: are angle brackets around email address allowed for auto-key-locate?
On Wed, 2019-10-16 at 20:26 +0200, David Hebbeker wrote: > 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 ""? > > > > That is fine. > > I have experienced a behavior I could only explain with auto-key- > locate being restricted to the pure form. I still have the problem described in my previous e-mail. Can it be that this is faulty behavior of the GnuPG? I would create a bug report at [1] so it does not get lost. Does something speak against it? David [1]: https://dev.gnupg.org/ 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
Re: are angle brackets around email address allowed for auto-key-locate?
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 ""? > > 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 "" msg.txt gpg: : 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 " 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 Davidkeyserver hkp://keyserver.ubuntu.com:80 # Used for encryption auto-key-locate keyserver # Used for verifying signatures auto-key-retrieve 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
Re: are angle brackets around email address allowed for auto-key-locate?
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 ""?
That is fine. Find below our test addresses.
Salam-Shalom,
Werner
ps.
Here is our test data set. The second string is the exepcted result, if
it is NULL we can't extract a mail address from the string:
{ "Werner Koch ", "w...@gnupg.org" },
{ "", "w...@gnupg.org" },
{ "w...@gnupg.org", "w...@gnupg.org" },
{ "w...@gnupg.org ", NULL },
{ " w...@gnupg.org", NULL },
{ "Werner Koch (test) ", "w...@gnupg.org" },
{ "Werner Koch (test)", "w...@gnupg.org" },
{ "Werner Koch ", NULL },
{ "Werner Koch ", NULL },
{ "", "f...@example.org" },
{ "", "f...@example.org" },
{ "<.f...@example.org>", ".f...@example.org" },
{ "", "fo...@example.org" },
{ "", "foo.@example.org" },
{ "", NULL },
{ "", NULL },
{ "", NULL },
{ "<@example.org>", NULL },
{ "", NULL },
{ "<@f...@example.org>", NULL },
{ " ()", "f...@example.org" },
{ " ()", "fo()o...@example.org" },
{ " ()", "fo()o...@example.org" },
{ "fo()o...@example.org", NULL},
{ "Mr. Foo ", "f...@example.org"},
{ "Surname, Forename | company ", "f...@example.org"},
/* The next one is for sure not RFC-822 correct but nevertheless
* the way gpg does it. We won't change it because the user-id
* is only rfc-822 alike and not compliant (think only of our
* utf-8 requirement). */
{ "\"\" ", "f...@example.org"},
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
are angle brackets around email address allowed for auto-key-locate?
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 ""? I need to ask as I have an interoperability issue with Gnome Evolution. Evolution specifies the email with angle brackets when encrypting. [1]: https://www.gnupg.org/documentation/manuals/gnupg/GPG-Configuratio n-Options.html#index-auto_002dkey_002dlocate 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
