> Any chance to also make a autopkgtest out of it for fido? I tried adding the regress/ tests as dep8, but in the end it didn't make sense to me. Thinking about SRUs, the dep8 run is very late in the process, only triggered after the sru was accepted. Catching these failures at build time is much quicker.
> I know we talked about how to get a authenticating device in there - > let us know what the last update on that is. I searched for some sort of software-based fido device, like softhsm[1] for DNS servers, but didn't find anything I could use. If we want something like that, it will have to be in q-a-t. I can still commit to do it, but given the security team's request was to at least enable regress/, I did that first, but at build time. I'm not sure I can get the q-a-t run, with a real fido device using usb passthrough in a vm, ready before the next freeze this monday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864439 Title: [MIR] libfido2, libcbor (dependencies of openssh) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcbor/+bug/1864439/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
