Re: [webauthn] Extensions need to define how their parameters convert to/from CBOR

There is a systematic problem here, that our types and conversions aren't precisely specified.

I disagree that this makes the specifications "useless". Certainly a hostile implementer could do the wrong thing, and we should fix that, but a benign implementer is going to reach for ["utf-8 encode"]( when converting "A single JSON string prompt." (which should probably be a DOMString) to "a CBOR text string" (i.e. UTF-8).

We're likely to end up with some ordering inconsistencies in the more complex conversions, but HTML4 wasn't "useless" despite having lots of that sort of problem.

GitHub Notification of comment by jyasskin
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 17 October 2017 04:56:13 UTC