Re: [webauthn] Consider requiring canonical CBOR throughout

I would very much like non-cannonical CBOR be supported from authenticator to client. 

In specific:
- **always use shortest encoding**: for example, when generating the authenticator data, it is much easier to reserve 2 bytes for the length and go back and correct them than precalculating the length, especially when your device supports extensions.
- **indefinite encoding**: again, it is much easier to generate an indefinite encoding tag for arrays and maps and terminate it accordingly. There are also some very interesting uses for indefinite encoding for byte strings.

I agree it would be nice if this was required towards the authenticator.

-- 
GitHub Notification of comment by jovasco
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/455#issuecomment-325739767 using your GitHub account

Received on Tuesday, 29 August 2017 17:41:34 UTC