Dave Korn wrote:
Also, we're going to add a link to the setup.exe gpg .sig file on the main
page; then the simple rule will be "If it has a gpg signature, it's the new
version".
The main page now says:
"The signature for setup.exe can be used to verify the validity of this
binary using this public key."
Since I am new to these things, my simple question is: How?
I have tried (after the download of .sig, .asc and .exe files):
$ gpg --verify setup.exe.sig setup.exe
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: Signature made [...]
gpg: Can't check signature: public key not found
TIA,
Angelo.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
