Re: gpg4win expired code signing cert; please renew.

"Robert J. Hansen via Gnupg-users" <[email protected]>
Newsgroups gmane.comp.encryption.gpg.user
Message-ID <[email protected]>
> By the way, one doesn't need Microsoft's OS for checking the signature. Using
> Linux it's pretty simple to check the certificate that was used. First we
> extract the signature:
> ```
> $ osslsigncode extract-signature -pem -in gpg4win-5.0.0-beta369.exe \
> -out gpg4win-5.0.0-beta369.exe.pem
> PE checksum   : 028F186B
> Succeeded
> ```

FWIW, although I'm grateful osslsigncode exists I often find it to be 
unpleasant to use at the command line. Several months ago I wrote a 
Python script to make it easier for me, and a couple of other people 
have reported it makes their workflow easier.

https://github.com/rjhansen/signtool

_______________________________________________
Gnupg-users mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-users
OpenPGP_signature.asc (application/pgp-signature, 236 B)
-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQR9jsS4W2/t1sENPHkeepTU6H+R1QUCaPK4qwUDAAAAAAAKCRAeepTU6H+R1eah
AP9dzKPd5VRyrb45gwBmBKHxkUsacyk1ohy9FsdITa4TWAEA/vdy3KXrgn8PuLri6iGIHEfARKg5
rfcJ/7k1wJf2Wws=
=YwMd
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.