removing the secmem warning
Nick Wilson
nick@explodingnet.com
Mon Jan 7 19:47:01 2002
--OgqxwSJOaUobr8KG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
* Frank Tobin <ftobin@neverending.org> [020107 19:37]:
> I'd like to question the need for the secmem warning. Do you actually
> think it is useful? I am coming to the conclusion that it is only causing
> confusion among users. As the GnuPG users crowd widens, we're only going
> to see more of the same issue of people asking "what is this error?".
>=20
> It's not the asking that is the problem; it is a symptom of many users
> being confused, many that *aren't posting* and think there is a problem
> with their GnuPG. FAQ's don't help unless they are integrated with the
> software (GnuPG's FAQ isn't). manpages help a bit, but they are reference
> manuals, not help systems.
>=20
> Hence, I suggest that by default, there no secmem warning, and that there
> should be an alternate option "secmem warning" which turns it on.
>=20
> What sayeth you?
Right with you on that score.
--=20
Nick Wilson
Tel: +45 3325 0688
Fax: +45 3325 0677
Web: www.explodingnet.com
--OgqxwSJOaUobr8KG
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8Oe1DHpvrrTa6L5oRAphIAJ4jYNK7+hZn27c4LCJeM3VBa1ksUgCfeUwG
jo7DCV100/6ImiwJMbryf08=
=2Rpy
-----END PGP SIGNATURE-----
--OgqxwSJOaUobr8KG--