-
Notifications
You must be signed in to change notification settings - Fork 18
Allow unknown CBOR fields (ref #66) #110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some thoughts
cdf44b4
to
bc946b7
Compare
d01862e
to
6273416
Compare
6273416
to
c4ba62c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good to me! I added two small comments, but good to go as is.
map.insert(1, 10u8); | ||
map.insert(2, 20u8); | ||
|
||
let cbor = to_vec(&map).unwrap(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not necessarily for this PR, but I wonder if we could have additionally actual raw (cbor) bytes in these tests to compare the outputs to.
fn eq(&self, other: &Self) -> bool { | ||
match (self, other) { | ||
(CborError::SerdeCbor(e1), CborError::SerdeCbor(e2)) => { | ||
e1.to_string() == e2.to_string() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could implement PartialEq
in serde_cbor for this, because this is really ugly :D
But obviously, not for this PR.
## 1. Tungstenite now requiring selecting a crypto provider A panic at runtime when attempting to establish a secure WebSocket connection: ``` DEBUG tokio_tungstenite::tls::encryption::rustls: Added 148/148 native root certificates (ignored 0) thread 'main' panicked at /home/afresta/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/rustls-0.23.27/src/crypto/mod.rs:249:14: no process-level CryptoProvider available -- call CryptoProvider::install_default() before this point note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` For more details, see: * snapview/tokio-tungstenite#336 * snapview/tokio-tungstenite#353 This is now fixed by explicitly selecting `rustls` as the `tungstenite` TLS backend, as recommended in `tokio-tungstenite`. ## 2. Hybrid initial GetInfo deserialization fails An error deserializing the caBLE initial message containing the GetInfo response: ``` DEBUG libwebauthn::transport::cable::tunnel: Responding to GetInfo request with cached response ERROR webauthn_make_credential{dev=CableChannel}:ctap2_get_info: libwebauthn::proto::ctap2::protocol: Failed to parse Ctap2GetInfoResponse from CBOR-data provided by the device. Parsing error: SerdeCbor(ErrorImpl { code: Message("invalid type: byte array, expected Ctap2GetInfoResponse"), offset: 0 }) thread 'main' panicked at libwebauthn/examples/webauthn_cable.rs:139:10: called `Result::unwrap()` on an `Err` value: Platform(InvalidDeviceResponse) note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` This was accidentally introduced in #110: https://github.com/linux-credentials/libwebauthn/pull/110/files#diff-d061af4011a3c577c5c2dbef3b1933b0e8c8a9ebc0bf70a0ebc3358e890ed725R587 Fixed by using the appropriate serialization method.
Depends on trussed-dev/serde-indexed#19.