Marc-Andre Lureau

@AkihiroSuda feel free to open / move the bug to libslirp. fwiw, I am not exactly impressed by libslirp. The code is showing age, and has seen a number of...

Learn how it was built, eventually try to build it myself.

As long as nothing is using the actual system printf(), that should work. But that could have surprise consequences. I think we should really not #redefine system/lib macros...

> My logic here is that we had #define'd printf now for such a long time that this seems to be the simplest fix. My point is that this is...

From IRC discussion with Stefan: 10:21 some of the crypt algorithms (like key generation) were probably opened up so they can be cancelled, which is a features stemming from the...

Are enabled capabilities saved with the vTPM state? how/where? Can we add options to selectively enable/disable TPM capabilities during manufacturing? (new swtpm_setup option)

> > Can we add options to selectively enable/disable TPM capabilities during manufacturing? (new swtpm_setup option) > > No. Just disabling capabilities doesn't help to keep an upgrade path alive....

I test the build with the pending Fedora package: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2119295 ``` export PKG_CONFIG_SYSROOT_DIR=/usr/x86_64-w64-mingw32/sys-root/mingw/ export PKG_CONFIG_PATH=/usr/x86_64-w64-mingw32/sys-root/mingw/lib/pkgconfig cargo build --target x86_64-pc-windows-gnu ```

afaik, it will require changes in mio, which in turns needs std support. This might take a while. see rust-lang/rust#56533

I don't feel like I am up for the task, sorry :) Any plan for release nevertheless?