From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarkko Sakkinen Subject: Re: Question on Linux TSS architecture design (kernel vs. user space access) Date: Fri, 18 Dec 2015 13:51:37 +0200 Message-ID: <20151218115137.GA4774@intel.com> References: <20151215233237.GA31965@obsidianresearch.com> <201512161652.tBGGqWPG019442@d03av04.boulder.ibm.com> <20151216171633.GB32594@obsidianresearch.com> <201512161721.tBGHLqXh009986@d03av03.boulder.ibm.com> <20151216174523.GC32594@obsidianresearch.com> <201512161804.tBGI47vu000331@d01av02.pok.ibm.com> <201512171533.tBHFXn35003792@d03av02.boulder.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tpmdd-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: "Wilck, Martin" Cc: "tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org" List-Id: tpmdd-devel@lists.sourceforge.net On Fri, Dec 18, 2015 at 12:21:01PM +0100, Wilck, Martin wrote: > > The only way to restrict this would be to only allow root access to > > the keyctl commands affecting the TPM. > > I'll leave it to Jarkko to comment on that. > Btw, wouldn't the "keys, trusted" API need some sort of resource > management, too? And wouldn't it make sense to merge that all into a > single TPM resource pool? Well this should have been done when the syscall was originally introduced. I think the right long term solution would be to do resource swapping mechnaism (like the LRU mechanism that I described). /Jarkko ------------------------------------------------------------------------------