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: <20170314212425.GA29359@obsidianresearch.com>
Date:   Tue, 14 Mar 2017 15:24:25 -0600
From:   Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To:     Peter Huewe <peterhuewe@....de>
Cc:     tpmdd-devel@...ts.sourceforge.net,
        Ken Goldman <kgold@...ux.vnet.ibm.com>,
        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 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..

Jason

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ