Date: Mon, 14 Jun 2010 10:54:44 +1000 From: Peter Jeremy <peterjeremy@acm.org> To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no> Cc: current@freebsd.org Subject: Protecting sensitive data [was Re: Cleanup for cryptographic algorithms vs. compiler optimizations] Message-ID: <20100614005444.GA57650@server.vk2pj.dyndns.org>
next in thread | raw e-mail | index | archive | help
--HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Jun-13 10:07:15 +0200, Dag-Erling Sm=F8rgrav <des@des.no> wrote: >You always overwrite passphrases, keys etc. as soon as you're done with >them so they don't end up in a crash dump or on a swap disk or >something. Which brings up an associated issue: By default, mlock(2) can only be used by root processes. It would be really handy if non-privileged processes could lock small amounts of VM so they can securely handle passwords, passphrases, keys, etc. MAC offers the option of allowing non-root processes access to mlock() but doesn't provide any restrictions on the amount of memory they can lock. --=20 Peter Jeremy --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkwVfdQACgkQ/opHv/APuIc6aACfQQy/Ezb2KMT1H/Lz78DwlADk 3ysAn2jh3RBEgsRay4ld8m69v7CCGdCt =eIWx -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100614005444.GA57650>