linux-kernel - Re: [tpmdd-devel] [PATCH] tpm: Add sysfs interface to show TPM hardware version

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] [day] [month] [year] [list]

Message-ID: <20170315172556.GA6399@obsidianresearch.com>
Date:   Wed, 15 Mar 2017 11:25:56 -0600
From:   Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To:     James Bottomley <James.Bottomley@...senPartnership.com>
Cc:     Peter Huewe <peterhuewe@....de>, tpmdd-devel@...ts.sourceforge.net,
        linux-kernel@...r.kernel.org
Subject: Re: [tpmdd-devel] [PATCH] tpm: Add sysfs interface to show TPM
 hardware version

On Tue, Mar 14, 2017 at 02:42:51PM -0700, James Bottomley wrote:
> On Tue, 2017-03-14 at 15:24 -0600, Jason Gunthorpe wrote:
> > On Tue, Mar 14, 2017 at 07:58:37PM +0100, Peter Huewe wrote:
> > 
> > > > In practice, I suspect that a single user space application won't
> > > > support both TPMs. 
> > > Think of init scripts.
> > > Which daemon should it start?
> > 
> > Right, ideally we'd have a udev rule that triggers systemd to start
> > the userspace daemons when a TPM is detected, as other hardware does.
> > 
> > So whatever format we use has to be compatible with udev's matcher..
> 
> Technically, we have that already: my TPM2.0 detection stuff for udev
> triggers off the presence of the SUBSYSTEM=="tpmrm"  that matches any
> TPM2 device but not a 1.x one.

but long term tpmrm won't be TPM2 exclusive..

Jason