False insecure memory warnings...

[David Shaw]

--Kj7319i9nmIyA2yE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 03, 2003 at 02:55:50PM -0500, gabriel rosenkoetter wrote:
> After some discussion with David Shaw recently, I've broken down,
> admitted that my public keyring is really just huge and than having
> a cron job to maintain it is really pretty reasonable. So I've been
> blowing along happily with this in cron:
>=20
> 0 8 * * 1-5 zsh -c 'time gpg --no --batch --check-trustdb'
>=20
> (Yes, I really do want zsh's time output, thanks.)
>=20
> That was well and good till several days ago, when I started getting
> this:
>=20
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnupg.org/faq.html for more information
> gpg: checking at depth 0 signed=3D49 ot(-/q/n/m/f/u)=3D0/0/0/0/0/1
> gpg: checking at depth 1 signed=3D82 ot(-/q/n/m/f/u)=3D0/0/0/19/30/0
> gpg: checking at depth 2 signed=3D286 ot(-/q/n/m/f/u)=3D1/0/0/69/5/0
> gpg: checking at depth 3 signed=3D178 ot(-/q/n/m/f/u)=3D1/74/0/21/0/0
> gpg: next trustdb check due at 2003-04-16
> gpg --no --batch --check-trustdb  14.57s user 11.03s system 60% cpu 42.32=
8 total
>=20
> Only but my gpg(1) really is suid, I promise:
>=20
> uriel:~% which gpg
> /usr/pkg/bin/gpg
> uriel:~% ls -l `!!`
> ls -l `which gpg`
> -r-sr-xr-x  1 root  wheel  684660 Feb 27 07:27 /usr/pkg/bin/gpg*

I've seen this a few times before.  Check to make sure that there
isn't another copy of gpg somewhere, and the gpg that cron is running
is the same one that you're running from the shell.

David

--Kj7319i9nmIyA2yE
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2rc1 (GNU/Linux)
Comment: http://www.jabberwocky.com/david/keys.asc

iD8DBQE+jKpk4mZch0nhy8kRAjX5AJ9/2sZyedeOMnjTPwj4wcMkif0gXQCg2PNs
Cyhl910IaN4T3mgGYl7zvYo=
=nywP
-----END PGP SIGNATURE-----

--Kj7319i9nmIyA2yE--