chore(deps): bump libwebauthn to 0.5.0#166
Conversation
- Rename feature flags: libnfc/pcsc -> nfc-backend-libnfc/nfc-backend-pcsc - Migrate to the new from_json(RequestOrigin, PublicSuffixList, json) API - Convert NavigationContext to libwebauthn RequestOrigin (synthesise https://<rp.id> for AppId origins) - Use SystemPublicSuffixList::auto() to validate rpId - MakeCredentialRequest.cross_origin renamed to top_origin - CableQrCodeDevice::new_transient now takes a CableTransports arg (CloudAssistedOnly preserves legacy caBLE behaviour) - Assertion no longer exposes large_blob_key
c440113 to
4cabdba
Compare
|
FYI libwebauthn 0.5.0 added a |
|
My SoloKey is working again now!
Yup, enabling BLE L2CAP is great! I am having a problem testing hybrid in this build though. Filed linux-credentials/libwebauthn#225. I am going to go ahead and merge this since this fixes a USB CTAP for me, and hybrid on Android with up-to-date GMS wasn't working before anyway. |
iinuwa
left a comment
There was a problem hiding this comment.
Approving, with issue mentioned above
Bumps libwebauthn from 0.3.0 to v0.5.0.
Breaking: AppId origin requests now panic (
unimplemented!). As far as I understand, that code path is on its way out. HTTPS origin requests are unaffected.Runtime dependency: libwebauthn 0.5.0 validates rpId via the system Public Suffix List. credentialsd now needs the publicsuffix list package (
publicsuffix-list-dafsaon Fedora,publicsuffixon Debian/Ubuntu) present at runtime, otherwise requests fail. Out of scope for this bump: declaring it as an explicit packaging dependency, or bundling our own PSL implementation. (Sorry, I don't know enough about packaging.)Other changes are mechanical adaptations to libwebauthn API renames.