[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:
> I've tried the command line execution, finally with success (ie. 
> actually attempts to verify iso-sig). I get the sign date and an 
> RSA ID (752A3DB6) identifiable to the Tails RSAs available in the 
> key (ie. asc file) (98FEC6BC752A3DB6). It does not, and as far as
> I can see will never, produce what the Tails instructions say it 
> should, despite the Debian list number (I know Tails is based on 
> Debian, but still). Along with checksum, which I did with another 
> app, that will have to do: it shows the copy is genuine and comes 
> from Tails dev. I suggest to the Tails site people that these 
> issues should be addressed (warnings regarding Gpg4Win and 
> checksums, and whatever is going on with the verification ID 
> data).
> 

You should better ask that to <tails-ux at boum.org> and see if anyone
else can reproduce it.

I get fine printing both using the CLI method, as in the Linux CLI way
but in Windows, and GUI as in the Windows Kleopatra method.

Using tails-i386-1.4.iso and tails-i386-1.4.iso.sig

- -- 
Juan Miguel Navarro Martínez

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

iQEcBAEBCgAGBQJVZ7xMAAoJEELfPuRPJIB7W3MH/3FY7l9cmBa6g57Ctv+E1zEb
dIvaOrzgy0S30Y89AQMGT+vuxQNV9tiu68ef/YRtUi32Nz6JAdlwfeC3NkRCFYx0
StKA2P++6qzT1NR+2LeuHBNOhgvsb97NBzHU13M76HPhgtUyu7yDzQLnz9Bre2LA
9oNbmViKzCBiRlFU1wSmXIZLvzOYDnIx8BNun71PaAr3nuJ6Pg+nZWgAhDmuQqCQ
5b850hFfCnoylPrU0lsZuMGrYeeekFObMxSyHUz/fTxKDv++k9XkV9qFDK9Ho3ej
jeRZ2ynV08a9K8Bg4eWa1FyVvAwGpkcZXxuHyu7l1LckQ9SeTFGmzggBcUWeNG4=
=Yw36
-----END PGP SIGNATURE-----