Hi On Tue, May 2, 2017 at 8:59 PM Stefan Berger <stef...@linux.vnet.ibm.com> wrote:
> On 05/02/2017 12:05 PM, Marc-André Lureau wrote: > > Hi > > On Tue, May 2, 2017 at 3:53 PM Amarnath Valluri < > amarnath.vall...@intel.com> wrote: > >> This change introduces a new TPM backend driver that can communicate with >> swtpm(software TPM emulator) using unix domain socket interface. >> >> Swtpm uses two unix sockets, one for plain TPM commands and responses, >> and one >> for out-of-band control messages. >> >> > Let's not forget to mention the external protocol this backend rely on: > https://github.com/stefanberger/swtpm/wiki/Control-Channel-Specification > > The protocol documentation is quite limited. > > (I still question the need to rely on a public protocol, and a seperate > helper process project. If we had a qemu-swtpm, we could more easily evolve > the protocol in the future) > > > And who is going to implement that qemu-swtpm? Obviously this discussion > doesn't contribute to progress if nobody is doing that in the end. > The same persons who try to push for that emulated TPM code. The easiest approach would be to copy/adapt the swtpm code in qemu, if the licence is compatible. I can help with that if there is a consensus it's a better approach. -- Marc-André Lureau
