FS#74320 - [swtpm] PLEASE ENTER SUMMARY

Attached to Project: Community Packages
Opened by Derson5 (Derson5) - Sunday, 03 April 2022, 05:33 GMT
Last edited by Jonas Witschel (diabonas) - Monday, 18 April 2022, 08:11 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Shouldn't swtpm use fuse3 instead of fuse2? If I understand correctly, they are compatible.


Additional info:
* package version(s) swtpm 0.7.2
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon

Closed by  Jonas Witschel (diabonas)
Monday, 18 April 2022, 08:11 GMT
Reason for closing:  Upstream
Additional comments about closing:  Upstream targets fuse2, please open a feature request upstream if you would like to see fuse3 support
Comment by loqs (loqs) - Sunday, 03 April 2022, 19:51 GMT
swtpm has chosen to target fuse2 [1][2]. The pkgconfig file for fuse3 is fuse3 and the header is located in fuse3/cuse_lowlevel.h both of which would need to be manually changed to build with fuse3.
Have you contacted upstream about fuse3 support?

[1] https://github.com/stefanberger/swtpm/blob/v0.7.2/configure.ac#L211
[2] https://github.com/stefanberger/swtpm/blob/v0.7.2/src/swtpm/cuse_tpm.c#L57
Comment by Andrej Podzimek (andrej) - Friday, 15 April 2022, 10:51 GMT
Could this be somehow related to the fact that the software TPM configured in virt-manager has completely stopped working on all Windows clients? The swtpm update to 0.7.2 was the only recent major qemu-related change. Both CRB and TIS tpms produce almost the same error:

Device ACPI\MSFT0101\2&daba3ff&1 had a problem starting.

Driver Name: tpm.inf
Class Guid: {d94ee5d8-d189-4994-83d2-f68d7d41b0e6}
Service: TPM
Lower Filters:
Upper Filters:
Problem: 0x0
Problem Status: 0xC00000E5

(OTOH, this may well be unrelated; not sure to what extent the swtpm (mal)function depends on fuse versions.)
Comment by loqs (loqs) - Friday, 15 April 2022, 11:16 GMT
@andrej could that be  FS#74421 
Comment by Abdulkadir Furkan Şanlı (abdulocracy) - Sunday, 17 April 2022, 20:47 GMT
@andrej @loqs it appears to be incorrect file ownership in the local CA:  FS#74489 

Loading...