[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131009173847.GC18899@obsidianresearch.com>
Date: Wed, 9 Oct 2013 11:38:48 -0600
From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To: "Fuchs, Andreas" <andreas.fuchs@....fraunhofer.de>
Cc: Joel Schopp <jschopp@...ux.vnet.ibm.com>,
Leonidas Da Silva Barbosa <leosilva@...ux.vnet.ibm.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Rajiv Andrade <mail@...jiv.net>,
"tpmdd-devel@...ts.sourceforge.net"
<tpmdd-devel@...ts.sourceforge.net>,
Richard Maciel Costa <richardm@...ibm.com>,
"trousers-tech@...ts.sourceforge.net"
<trousers-tech@...ts.sourceforge.net>,
Daniel De Graaf <dgdegra@...ho.nsa.gov>,
Sirrix AG <tpmdd@...rix.com>
Subject: Re: [TrouSerS-tech] [tpmdd-devel] [PATCH 09/13] tpm: Pull everything
related to sysfs into tpm-sysfs.c
On Tue, Oct 08, 2013 at 09:15:55AM +0000, Fuchs, Andreas wrote:
> Rather than an ioctl, why not provide a different tpm-device per
> locality. This way, the access to the different localities can be
> restricted via standard user/group of the device. i.e. /dev/tpm0l1,
> /dev/tpm0l2, ... or similar approaches...
The way the TPM architecture is setup you will need the middle ware to
do the switching between localities and managing cross locality
resources, so it doesn't make sense for the kernel to export a
locality specific char device.
You'd have to do the above by having trousers create unix domain
sockets for each of the privilege levels and using the usual security
mechanisms to protect access to those sockets.
Jason
--
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