[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gpg4win-users-en
Subject:    Re: [Gpg4win-users-en] verify
From:       Bernhard Reiter <bernhard () intevation ! de>
Date:       2023-11-28 17:47:10
Message-ID: 202311281847.22891.bernhard () intevation ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Am Dienstag 28 November 2023 17:55:19 schrieb Frank Esposito:
> thanks for the info ----  I am new to all  this and it quite overwhelming
> just to  verify a file ----  

For the Gpg4win*.exe download, you don't, just check the code signature. :)

Otherwise you do it from the explorer, right click and select verify
on the signature.

If you want to do it on the command line as an exercise:

> from the syntax  of  --verify   how is the 
> public key  found/referenced?

The public key (short "pubkey") is imported earlier and then is found in your 
local key storage.

So it is just
   gpg --verify FILENAME

after you did an
  gpg --fetch https://gnupg.org/signature_key.asc

Or you download https://gnupg.org/signature_key.asc
and 
  gpg --import signature_key.as

If you want to see more about what is happening, you can add an `-v` after 
the 'gpg`, like 
gpg -v --fetch https://gnupg.org/signature_key.asc

Best Regards,
Bernhard


-- 
https://intevation.de/~bernhard    +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter

["signature.asc" (application/pgp-signature)]
[Attachment #6 (text/plain)]

_______________________________________________
Gpg4win-users-en mailing list
Gpg4win-users-en@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/gpg4win-users-en

[prev in list] [next in list] [prev in thread] [next in thread]