- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Jun 2021 20:09:02 +0000
- To: public-webauthn@w3.org
> The length of the public-key map is given explicitly. I think you're mixing that up with the credential ID length. The byte length of the public-key map is not given explicitly as it is implicit from the CBOR structure, and CBOR encodes the number of pairs rather than the byte length of the map. But yeah, you don't need any nonstandard CBOR parser but you do need one with an API that facilitates reading multiple concatenated values. For example the linked Chrome example seems to be reading a stateful byte stream so it can continue the second parse from where the first parse ended. Another option would be for the parser to return the end offset along with the parsed result (common in C APIs, for example). -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1614#issuecomment-853349584 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 June 2021 20:09:55 UTC