Insecure Memory Warning! ???.
Frank Tobin
ftobin@uiuc.edu
Thu, 19 Oct 2000 14:06:30 -0500 (CDT)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Werner Koch, at 14:26 +0200 on Thu, 19 Oct 2000, wrote:
> OTOH all the folks who asked about this have never read our man page:
As mentioned as the second part of my post, the warning, if not removed,
should have a pointer to documentation describing the warning. If you
want people to read the manpage, tell them:
gpg: Warning: using insecure memory! See BUGS in the manpage.
And in addition, add the following to BUGS in the manpage:
If this program is not installed as setuid(root), you may get a warning
such as "Warning: using insecure memory!". To ignore this warning, add
the option "no-secmem-warning" to your ~/.gnupg/options file.
If these two steps were done, I think this would solve a lot of user's
questions/problems/postings. Documenation is one thing one shouldn't
skimp on by any means. And having FAQ's is not the only way; you need
_linking_ between the documentation (hypertext or just plain textual
references is fine). Expecting users to blindly lookup answers in a FAQ
which isn't usuably available to 'normal' users is pretty unreasonable.
The only documentation available is the manpage, and there is no reference
to a FAQ in the manpage.
- --
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/
iEYEARECAAYFAjnvRjgACgkQVv/RCiYMT6N1fACgoafBDwJhrKKzhriVKsMq5HA2
V6MAoIaX/WuIT/X43lCan0W3vt+n1B+O
=8csc
-----END PGP SIGNATURE-----
--
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of "unsubscribe" to gnupg-users-request@gnupg.org