[Gpg4win-users-en] Problems with Gpg4Win Verification Operations (and a couple of apparent bugs)

[Juan Miguel Navarro Martínez]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

L:
> 3) I will also try trusting the Tails key using my own key; still, 
> Gpg4Win does offer the ability to " completely trust" a key without
> using your own, and even when this is the case, the key fails to
> appear in Kleopatra's trusted field, also an apparent bug. If the
> trusted field only admits keys when signed with your own, this
> should be made clear.
> 

You can give a trust level using command-line but it won't affect
Kleopatra "Trusted keys" list, it only will show if you sign it with
your own key.

I would try and confirm it but I'm having some problems here.

> 4) This still fails to account for the unidentified string (short 
> and post-key-imported long), unmatched to anything on the Tails 
> site, the real issue. Can anyone account for this string 
> (/0xBA2C222F44AC00ED9899389398FEC6BC752A3DB6)?
> 
That's Tails developers signing subkey:

https://paste.debian.net/183806/

See the second key fingerprint, it matches the 0xFingerprint key ID
format you typed.


- -- 
Juan Miguel Navarro Martínez

GPG Keyfingerprint:
5A91 90D4 CF27 9D52 D62A
BC58 88E2 947F 9BC6 B3CF
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJVY+piAAoJEELfPuRPJIB7TMAIAL5u5Q2YMCw2dR+CGgLxte8w
OaPz7UYKUSUCXMu5SOOUE0ADDQHLphgHqF3RpXDNVIuZa7IqvwlfbRkbASBseHlD
53r2ks7upOFLOZQtmvZRzn+mckxiHJ6QJGMjPeE/FvsX+X/1/3AMPAsYFzxeuArQ
6xID8n0qxmDnC5vSTCtOqPcVj+ZuLQe+7OlNbwfAVhGYI40ITEtVSTZdhTFVRSLO
PQAdR/b8dF8Ju6oE0ZfofSaODc6M8o8+Xj1MNC/Xv4UxIul3fFHyFHVF4v9mCDfQ
BKWR1h3oP9p+PYoxm6b2br8vVmKQ0idwSYhKUe92u5SNRhhFnAE2zML8Aq8gHZM=
=5AH0
-----END PGP SIGNATURE-----