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.
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: https://github.com/jstedfast/MimeKit/blob/f3db67a73ec3dae89aee7105e9af94a412078b98/MimeKit/Cryptography/OpenPgpContext.cs#L664