[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <AEF7FD5A-F622-46A1-8034-2FAF10CEBA46@mac.com>
Date: Tue, 15 Jan 2008 21:24:00 -0500
From: Kyle Moffett <mrlinuxman@....com>
To: David Howells <dhowells@...hat.com>
Cc: 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
On Jan 15, 2008, at 18:46, David Howells wrote:
> (*) 01-keys-inc-payload.diff
> (*) 02-keys-search-keyring.diff
> (*) 03-keys-callout-blob.diff
One vaguely related question: Is there presently any way to adjust
the per-user max-key-data limit? I've been tinkering with using the
new-ish MIT kerberos "KEYRING:" credentials-cache code to hold keys
for persistent daemons. Unfortunately "root" keeps hitting the limit
even with only about 16 keys allocated across a few sessions. After
perusing the docs I can't find any documentation on adjusting the
limits.
I'd really like some way to specifically allow root to allocate up to
several megs worth of non-swappable key data, although I suppose just
increasing the global limit slightly wouldn't be bad either. If such
functionality already exists then I'd appreciate a pointer to it (and
possibly respond in kind with documentation patches).
Cheers,
Kyle Moffett
--
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