You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
It appears that there is an issue with a PGP key server query building. The current format for constructing the request leads to leading zero(s) (if present) of 'keyid' being omitted. Which in turn causes an "Invalid request/Not found" error on a key server. Tested on keys.openpgp.org, keyserver.ubuntu.com and pgp.mit.edu.
Expected behavior
The format string in code should be updated to "op=get&search=0x{0:X16}" to correctly represent keyId as a fixed-width string of 16 hex digits:
Describe the bug
It appears that there is an issue with a PGP key server query building. The current format for constructing the request leads to leading zero(s) (if present) of 'keyid' being omitted. Which in turn causes an "Invalid request/Not found" error on a key server. Tested on keys.openpgp.org, keyserver.ubuntu.com and pgp.mit.edu.
Examples:
https://keys.openpgp.org/pks/lookup?op=get&options=mr&search=0x04376F3EE0856959 (valid)
https://keys.openpgp.org/pks/lookup?op=get&options=mr&search=0x4376F3EE0856959 (error)
Platform:
Expected behavior
The format string in code should be updated to
"op=get&search=0x{0:X16}"
to correctly representkeyId
as a fixed-width string of 16 hex digits:MimeKit/MimeKit/Cryptography/OpenPgpContext.cs
Line 664 in f3db67a
The text was updated successfully, but these errors were encountered: