| 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
| ||
|
Date: Thu, 08 Aug 2013 15:46:45 +0100 From: David Howells <dhowells@...hat.com> To: Nico Williams <nico@...ptonector.com> Cc: dhowells@...hat.com, keyrings@...ux-nfs.org, linux-nfs@...r.kernel.org, simo@...hat.com, linux-kernel@...r.kernel.org, krbdev@....edu Subject: Re: [PATCH 1/2] KEYS: Implement a big key type that can save to tmpfs Nico Williams <nico@...ptonector.com> wrote: > b) how to create tmpfs locations in which to store credentials (which > can be unbounded in size, so storing them in the kernel is silly; Ummm... tmpfs stores them in the kernel too - though it can page them out to swap. I have altered my big-key implementation to just store small items in an internal buffer and big items in a tmpfs file. This means that small items will use up _less_ kernel memory if they're in a key because they won't require the overhead of a dentry struct and an inode struct. > (b) can be solved in many ways, and the simplest is to have a > filesystem where top-level directories named after UIDs "exist" as > soon as they are referenced and as long as they are non-empty. You > can use autofs + tmpfs, or a variant of tmpfs for this. Don't forget to add user namespaces into the mix :-/ David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists