linux-kernel - Re: [PATCH 00/26] Permit filesystem local caching

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: <30682.1200502531@redhat.com>
Date:	Wed, 16 Jan 2008 16:55:31 +0000
From:	David Howells <dhowells@...hat.com>
To:	Kyle Moffett <mrlinuxman@....com>
Cc:	dhowells@...hat.com, sds@...ho.nsa.gov, casey@...aufler-ca.com,
	Trond.Myklebust@...app.com, npiggin@...e.de,
	linux-kernel@...r.kernel.org, selinux@...ho.nsa.gov,
	linux-security-module@...r.kernel.org
Subject: Re: [PATCH 00/26] Permit filesystem local caching

Kyle Moffett <mrlinuxman@....com> wrote:

> One vaguely related question:  Is there presently any way to adjust the
> per-user max-key-data limit?

There's no reason there can't be.  It just needs a policy deciding.  Do we
have:

 (1) One control for all.

 (2) One control for all non-root users; no quotas on root.

 (3) One control for root, one control for all non-root users.

 (3) Separate controls for all users.

Should this be a ulimit?  Should a non-root user be able to adjust their own
quotas within limits set by root?

How should the quota be accessed?  The obvious way is to have /proc or /sys
controls.

Non-root quotas tend to be transitory.  When the user_struct pinning them goes
out of scope, they tend to disappear.  How do we recover the settings, if at
all?

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/