Open dustymabe opened 6 years ago
FYI - I changed the gpgkeypath ostree remote config setting in between running the two status commands.
This is probably an ostree issue. Will check.
Hmm, so I think that's just a consequence of how commits are signed and verified. The commit signature only includes the short id of the signing fingerprint. If the public key is not provided, then ostree (really, GPGme) can only provide the short id from the signature. OTOH, if the key is given, we can use its full fingerprint.
I'll let @cgwalters confirm this in case I'm missing something.
So, I would also be interested why rpm-ostree status
(Without -v
) gives the key ID/fingerprint by default, rather then the UID (GPGSignature: Valid signature by Fedora 27 <fedora-27@fedoraproject.org>
probably says more to users than a key ID/fingerprint).
In one case I see
E08E7E629DB62FB1
and in the other case I see128CF232A9371991C8A65695E08E7E629DB62FB1
. Do these need to be the same or was this change intentional?