On 1/9/20 3:41 AM, Michał Górny wrote:
Dnia January 9, 2020 5:11:46 AM UTC, Salah Coronya <salah.coro...@gmail.com>
napisał(a):
On 1/8/20 3:16 PM, Mikle Kolyada wrote:
app-crypt/tpm-tools
app-crypt/tpm2-abrmd
app-crypt/tpm2-tools
app-crypt/tpm2-totp
app-crypt/tpm2-tss-engine
app-crypt/tpm2-tss
app-crypt/trousers
I would be interested in proxy-maintaining the TPM/TPM2 related
package,as I use most of the packages (I have a physical TPM 1.2 and a
VM with a virtual TPM 2.0), and the one's I don't yet use are closely
related to ones I do use and are easy enough to maintain as well. Not
interested in app-crypt/tpm-emulator, as its functionality by a is
superseded by a package i maintain, app-crypt/swtpm.
Do you think that tpm-emulator is worth keeping, or should it be last rited in
favor of swtpm?
--
Best regards,
Michał Górny
I don't think tpm-emulator is worth keeping. It should probably be last
rited. The only thing I can think of that tpm-emulator has swtpm doesn't
are initscripts, but I can add some if its needed. Normally swtpm will
be started by qemu (for VMs) or (when used in tests) launched by the
test suite. It is certainly capable of being used as a system-wide
daemon to create a virtual TPM device or socket, though.
