post-installation questions

[Sebastian Wiesinger]

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

* Tuomas Pellonpera <tp58494@uta.fi> [2001-10-07 13:38]:
> Hi!

Hi Tuomas

> Yesterday, I installed GnuPG 1.0.6 on my Debian GNU/Linux system (2.2r). I
> think I got GnuPG installed successfully, but two details confuse me.
>=20
[.. Can't help you with 1.) ..]
>=20
> 2.)
> This may be more serious. Everytime I run gpg, it prints out this
> complaint, "Warning: using insecure memory." How serious is this, and what
> could be done about it?

,------[GnuPG FAQ]
| 6.1) Why do I get "gpg: Warning: using insecure memory!"=20
| On many systems this program should be installed as setuid(root).
| This is necessary to lock memory pages. Locking memory pages
| prevents the operating system from writing them to disk and thereby
| keeping your secret keys really secret. If you get no warning
| message about insecure memory your operating system supports locking
| without being root. The program drops root privileges as soon as
| locked memory is allocated.=20
`------

Greetings
Sebastian
--=20
Sebastian Wiesinger <bofh@fire-world.de>
GPG Key-ID: 0x76B79F20
Fingerprint: F7C9 2DA7 ED4C 17B7 1523  98F5 1B60 34F4 76B7 9F20

--+HP7ph2BbKc20aGI
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Weitere Infos: siehe http://www.gnupg.org

iD8DBQE7wH02G2A09Ha3nyARAsE/AJ9IINEPwhgCrMV+a1yJlkaq8OslIwCghFMt
MAwrfORUNDQ3Xj5vSI7dPXA=
=yw/z
-----END PGP SIGNATURE-----

--+HP7ph2BbKc20aGI--