This is the mail archive of the
mailing list for the Cygwin project.
Re: gpg: can't lock memory: Permission denied
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 05 Apr 2010 13:18:10 +0100
- Subject: Re: gpg: can't lock memory: Permission denied
- References: <4BB9C8D1.firstname.lastname@example.org>
On 05/04/2010 12:26, Ulrich Jakobus wrote:
> gpg: can't lock memory: Permission denied
> Anybody else also seeing this, i.e. general problem, or just for me?
I'm similarly right up-to-date, and at least a trivial test of verifying a
signature worked for me:
> $ wget http://cygwin.com/setup.exe http://cygwin.com/setup.exe.sig
> --2010-04-05 13:16:59-- http://cygwin.com/setup.exe
[ ... snip ... ]
> FINISHED --2010-04-05 13:17:07--
> Downloaded: 2 files, 640K in 7.7s (83.1 KB/s)
> $ gpg -v setup.exe.sig
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnupg.org/faq.html for more information
> gpg: assuming signed data in `setup.exe'
> gpg: Signature made Tue Mar 23 16:00:02 2010 GMTST using DSA key ID 676041BA
> gpg: using PGP trust model
> gpg: Good signature from "Cygwin <cygwin@[REDACTED AGAINST SPAM]>"
> gpg: binary signature, digest algorithm SHA1
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple