Stefan Winter
Stefan Winter
FWIW, same issue here. Attaching a -vvv output. [Uploading check_yum.txt…]()
That didn't work so well apparently. Copy&Pasting like above: Nagios Plugin for Yum updates on RedHat/CentOS systems - Version 0.11.3 Author: Hari Sekhon setting plugin timeout to 30 seconds running...
Not sure where the complexity lies when Chromium upstream supports FIDO2/WebAuthn and CTAP2 already? Even Firefox on my e/OS with microG interfaces correctly with the authenticator parts in recent microG....
Here is a bin2hex of attestation objects. Yubikey 5C, parsing fine: Attestation Object in bin2hex: `a363666d74646e6f6e656761747453746d74a068617574684461746158c42321cf6a3d265802762dd143fd886c7474c2e0ed2582d5f8fc0dbc58c4580a4c41000003f20000000000000000000000000000000000401e65dd64feaf2d9040bcb6111c423ac4174e2a6e56297a24e0d2bd25ff1b6d14e08439eae75b795e429539dac23b9517c061f0083a4eeb52b40c73d6ec812666a50102032620012158202ad6d5c4b5574b7425fb5ca94bc6af6609e189daa77de72dfd722aba2e5c5d8b225820b9d869629e1ffd14e0da113f88616fa5c853c62e2e2e2a89d584267d40547c77` FaceID in iOS 16.1.1 (iPhone 14 Pro), not parsing correctly: Attestation Object in bin2hex:...
FWIW, the reg ceremony produced the identical byte sequence in Safari and Chrome. (But as I wrote above, the demo reg on webauthn.io worked with that FaceID which is somewhat...
Considering that we are talking about an iPhone, the debug options are limited client-side, sorry. (Besides, it's not my phone and I need to pester a colleague to do this)....
Well, even using a Yubikey Bio does not work there (or somehow). Registration worked after a few attempts but then gave me GET https://webauthn.spomky-labs.com/profile 500 (Internal Server Error)
So my colleague registered FaceID working(!) with the user identifier testiphone14faceid. I hope you have enough server-side debug to see attestation data...
I also have a use case for an interactive authproc (MFA with the simplesamlphp-module-webauthn). Being able to run interactive authprocs would be a very valuable addition.
I have myself not deployed on 2.1 yet (but the module does work on 2.0.6). Any chance you can try with 2.0.x and see if the error is reproducible there?