Hello,
it would be nice if keys could also be selcted by their sha2 fpr which gpgsm --list-keys already displays
Hello,
it would be nice if keys could also be selcted by their sha2 fpr which gpgsm --list-keys already displays
BTW, fingerprints for X.509 are not well defined because you get a different one when changing the *unsigned" attributes. Not a common case but one should be aware of it.
The problem here is that we don't have the sha-2 fingerprint in our SQL tables. Thus we would not only need to do a full table search but also parse the actual blob to compute the sha-2 fingerprint.
Noet that for PGP v5 keys we store the 32 octet SHA-2 fingerprint but we do not store a SHA-1 fingerprint for such a key.