verify output
Kristian Fiskerstrand
kristian.fiskerstrand at sumptuouscapital.com
Wed Jul 30 17:44:01 CEST 2014
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 07/30/2014 05:35 PM, Werner Koch wrote:
> On Wed, 30 Jul 2014 14:52,
> kristian.fiskerstrand at sumptuouscapital.com said:
>> I was thinking more along the lines of
>
...
>
> Ah yes. However, is the subkey fingerprint really useful? It may
> lead to more confusion. We usually try to hide the fact that there
> are subkeys and present only the primary fingerprint. What about
> this?
>
Not except for the point you're making below re keyid mismatch.
> or with the new algorithm info format:
>
> --8<---------------cut here---------------start------------->8---
> gpg: Signature made Wed Jul 30 10:08:40 2014 CEST using
> dsa2048/77F95F95 gpg: key fingerprint 8061 5870 F5BA D690 3336
> 86D0 F2AD 85AC 1E42 B367 gpg: Good signature from "Werner Koch
> <wk at gnupg.org>" gpg: aka "Werner Koch
> <wk at g10code.com>" gpg: aka "Werner Koch <werner at
> eifzilla>" --8<---------------cut
> here---------------end--------------->8---
I prefer this one myself
>
> All of them will lead to the question why the keyid does not match
> the fingerprint. However, this can easiliy be explained in the
> FAQ.
>
Indeed.
> Should we print the fingerprint if for a /BAD signature/, too?
It is most important for when a key is not available to verify at least.
- --
- ----------------------------
Kristian Fiskerstrand
Blog: http://blog.sumptuouscapital.com
Twitter: @krifisk
- ----------------------------
Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
- ----------------------------
Veni vidi velcro
I came, I saw, I got stuck
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJT2RK+AAoJEPw7F94F4TagmfoP/RmfuZXcqVVpXs4DLSG5xUMw
F0XnEdFd0bWJyYmIevk1oQ5hScgesFfC3YtHboKyALRHQtzVYQQrWSjKwEv6YtpI
5/7HPaIHcBzyGs3LX97gG/wIBQXv699iJGe9760c6v2JBAiZZSb69DU6/A/6w/wj
imZ7TD1qNESMDwmAHmhgkBRRDiFMyDkbI/xSlHV2Zl51TIVGVW3gSppNbk/b4rKI
zT811iODJ9Z8g5mK2mZcylIPG/FHEtr+ZFWKoUIk23+pzK8u7JMcBGGkiMOSghec
KVGd85qaHPb7oHOjvXlevakqDiIb/ITfWDUju3mJ0S7YMgSVRNaE4VZE/IGDeOoa
vohi4nBBBph8x4048cT4s9Qo2T3jP6G/tQ7yufGhwKS0dVeDqzO9d24xovHCh8+m
wnuO7qSHUE14p27lkMF4eFZaSAF0P7MfGlqfpizIdDkqwznJpcxCiKG0mD9jueF2
0vbOASWmRLJ8ZlmdUwjH7OBtrZiYqPsK9DFyi3f8imLIWb+Y9mZF9fVbKDgc5AaH
AH1iHEG5Qmls8ZxXFDtxiH3ROYkFctu+cSW1lYT5UT7+++SRqJ4MKn6voWnX3vVG
r6w/tvBQ8MNj02rwm5UVTUSBptI2RzNkhOKkHAry2PA6GqZcA7djeQR3o7LvJaFS
9KSHWOqbZCnYkJ2DbD96
=kL3f
-----END PGP SIGNATURE-----
More information about the Gnupg-devel
mailing list