linux-kernel - Re: Revised keyrings(7) man page for review

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <30566.1481638837@warthog.procyon.org.uk>
Date:   Tue, 13 Dec 2016 14:20:37 +0000
From:   David Howells <dhowells@...hat.com>
To:     "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
Cc:     dhowells@...hat.com, lkml <linux-kernel@...r.kernel.org>,
        Eugene Syromyatnikov <evgsyr@...il.com>,
        keyrings@...r.kernel.org, linux-man <linux-man@...r.kernel.org>
Subject: Re: Revised keyrings(7) man page for review

Michael Kerrisk (man-pages) <mtk.manpages@...il.com> wrote:

>               The payload data may  be  stored  in  a  tmpfs  filesystem,
>               rather  than in kernel memory, if the data size exceeds the
>               overhead of storing the data in the  filesystem.   (Storing
>               the  data in a filesystem requires filesystem structures to
>               be allocated in the kernel.  The size of  these  structures
>               determines the size threshold above which the tmpfs storage
>               method is used.)  Since Linux  4.8,  the  payload  data  is
>               encrypted when stored in tmpfs, to prevent it being written
>               unencrypted into swap space.

"... thereby preventing it from being written unencrypted into the swapspace"?

David