Insecure Memory Warning! ???.

[Marcelo C . Martinelli]

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

On Wed, Oct 18, 2000 at 08:11:00PM -0500, Frank Tobin wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Mark.Keisler@motorola.com, at 17:39 -0500 on Wed, 18 Oct 2000, wrote:
>=20
> > > > > # gpg: Warning: using insecure memory!
>=20
> Seriously, given the amount of times this is posted to this mailing list,
> this warning needs to disappear, or point the user to some relevant
> documentation on why it is appearing, and how to remedy it.
>=20
> - --=20
> Frank Tobin		http://www.uiuc.edu/~ftobin/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.4 (FreeBSD)
> Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/
>=20
> iEYEARECAAYFAjnuSiYACgkQVv/RCiYMT6PMcACgmKh4VQXCIk5laC0ooJ+O7Sn6
> xAUAoIodKgDotk4WBYovOqfAyZkyOJWX
> =3DdyTE
> -----END PGP SIGNATURE-----
>=20
> --=20
> Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
> with a subject of  "unsubscribe"  to gnupg-users-request@gnupg.org
>=20

IMHO, a good way to avoid having users constantly complain about this
warning, is to create a no-secmem-warning entry by default in the
~/.gnupg/options file when a user first runs gpg. Eventually, users
will edit the file anyways!

--
Marcelo C. Martinelli <mcm@hvymtl.org>

--gKMricLos+KVdGMg
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.3 (FreeBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE57vZkLbA1bZ5Ju+wRAv+5AJ9NEJjPYMfFt5D9yU0L1Wyju7xQmQCfZEDL
mqyhDhNFPpoe3MMo7y1e9lk=
=MH9V
-----END PGP SIGNATURE-----

--gKMricLos+KVdGMg--

-- 
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of  "unsubscribe"  to gnupg-users-request@gnupg.org