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
| ||
|
Message-ID: <20190417172628.GF435@sasha-vm> Date: Wed, 17 Apr 2019 13:26:28 -0400 From: Sasha Levin <sashal@...nel.org> To: "Enrico Weigelt, metux IT consult" <lkml@...ux.net> Cc: peterhuewe@....de, jarkko.sakkinen@...ux.intel.com, jgg@...pe.ca, corbet@....net, linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org, linux-integrity@...r.kernel.org, linux-kernel@...rosoft.com, thiruan@...rosoft.com, bryankel@...rosoft.com Subject: Re: [PATCH v3 2/2] ftpm: add documentation for ftpm driver On Wed, Apr 17, 2019 at 02:23:13PM +0200, Enrico Weigelt, metux IT consult wrote: >On 15.04.19 17:56, Sasha Levin wrote: > >Hi, > >> +The driver acts as a thin layer that passes commands to and from a TPM> +implemented in firmware. The driver itself doesn't contain much logic >and is> +used more like a dumb pipe between firmware and kernel/userspace. >Is that TPM already used in production or yet an PoC ? >IOW: can the protocol be changed ? Sadly no, this is based on something that exists for a few years already and we're trying to make Linux run on it. -- Thanks, Sasha
Powered by blists - more mailing lists