secmem patch

Christian Kurz
Sat, 21 Oct 2000 14:28:16 +0200

Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 00-10-20 Dan Boger wrote:

> with all the questions about secmem, I figured a simple pointer can help,
> without installing insecure options by default. This was against 1.0.4,
> but I believe it'll work with older versions as well.
Why? There's README in the src-package and point 8 of the install parapraph already explains the problem and the fix. So, I expect the binary packages to also install this file into the documentation directory of GnuPG. If the users refuse to read the documentation first or look there for some help about this warning message, they don't need other hints. It's always good style to read first the documentation and then ask for help on a mailing-list. So I would suggest not including your patch in GnuPG, as the hints are already visibel enough. Ciao Christian --=20 While the year 2000 (y2k) problem is not an issue for us, all Linux implementations will impacted by the year 2038 (y2.038k) issue. The Debian Project is committed to working with the industry on this issue and we will have our full plans and strategy posted by the first quarter of 2020. --p8PhoBjPxaQXD0vg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4a (GNU/Linux) Comment: For info see iEYEARECAAYFAjnxi+AACgkQqeZn/ybMeFMvBwCffJ5N5vNppORwLx5JckbSd1k3 SFQAoIIholSX8frLZvYlYq8lW1PVK4Mz =HjJU -----END PGP SIGNATURE----- --p8PhoBjPxaQXD0vg-- -- Archive is at - Unsubscribe by sending mail with a subject of "unsubscribe" to