Skip to content

Commit

Permalink
fix #455: we are using CTAP canonical CBOR encoding form everywhere (#…
Browse files Browse the repository at this point in the history
…731)

* fix #455: we are using CTAP canonical CBOR encoding form everywhere

* incorp akshayku's comment, thx!
  • Loading branch information
equalsJeffH authored and jcjones committed Jan 3, 2018
1 parent 950f574 commit 7be2d3d
Showing 1 changed file with 22 additions and 8 deletions.
30 changes: 22 additions & 8 deletions index.bs
Expand Up @@ -113,6 +113,11 @@ spec: page-visibility; urlPrefix: https://www.w3.org/TR/page-visibility/
spec: WHATWG HTML; urlPrefix: https://html.spec.whatwg.org/
type: dfn
text: focus

spec: FIDO-CTAP; urlPrefix: https://fidoalliance.org/specs/fido-v2.0-ps-20170927/fido-client-to-authenticator-protocol-v2.0-ps-20170927.html
type: dfn
text: CTAP canonical CBOR encoding form; url: message-encoding

</pre> <!-- class=anchors -->

<!-- L128 spec:webappsec-credential-management-1; type:dictionary; for:/; text:CredentialRequestOptions -->
Expand Down Expand Up @@ -248,7 +253,15 @@ external hardware, or a combination of both.

## [RPS] ## {#conforming-relying-parties}

A [=[RP]=] MUST behave as described in [[#rp-operations]] to get the security benefits offered by this specification.
A [=[RP]=] MUST behave as described in [[#rp-operations]] to obtain the security benefits offered by this specification.

## All Conformance Classes ## {#conforming-all-classes}

All [=CBOR=] encoding performed by the members of the above conformance classes MUST be done using the
[=CTAP canonical CBOR encoding form=].
All decoders of the above conformance classes SHOULD reject CBOR that is not validly encoded
in the [=CTAP canonical CBOR encoding form=] and SHOULD reject messages with duplicate map keys.


# Dependencies # {#dependencies}

Expand All @@ -261,11 +274,12 @@ below and in [[#index-defined-elsewhere]].
inclusion of any line breaks, whitespace, or other additional characters.

: CBOR
:: A number of structures in this specification, including attestation statements and extensions, are encoded using the Compact
Binary Object Representation (<dfn>CBOR</dfn>) [[!RFC7049]].
:: A number of structures in this specification, including attestation statements and extensions, are encoded using the
[=CTAP canonical CBOR encoding form=] of the Compact Binary Object Representation (<dfn>CBOR</dfn>) [[!RFC7049]],
as defined in [[!FIDO-CTAP]].

: CDDL
:: This specification describes the syntax of all CBOR-encoded data using the CBOR Data Definition Language (CDDL) [[!CDDL]].
:: This specification describes the syntax of all [=CBOR=]-encoded data using the CBOR Data Definition Language (CDDL) [[!CDDL]].

: COSE
:: CBOR Object Signing and Encryption (COSE) [[!RFC8152]]. The IANA COSE Algorithms registry established by this specification is also used.
Expand Down Expand Up @@ -4423,8 +4437,8 @@ Boris Zbarsky.
"FIDO-APPID": {
"authors": ["D. Balfanz", "B. Hill", "R. Lindemann", "D. Baghdasaryan"],
"title": "FIDO AppID and Facets",
"href": "https://fidoalliance.org/specs/fido-uaf-v1.1-rd-20161005/fido-appid-and-facets-v1.1-rd-20161005.html",
"status": "FIDO Alliance Review Draft"
"href": "https://fidoalliance.org/specs/fido-v2.0-ps-20170927/fido-appid-and-facets-v2.0-ps-20170927.html",
"status": "FIDO Alliance Proposed Standard"
},

"FIDO-U2F-Message-Formats": {
Expand All @@ -4438,8 +4452,8 @@ Boris Zbarsky.
"authors": ["R. Lindemann", "V. Bharadwaj", "A. Czeskis", "M. B. Jones", "J. Hodges", "A. Kumar", "C. Brand", "J. Verrept",
"J. Ehrensvard"],
"title": "FIDO 2.0: Client to Authenticator Protocol",
"href": "https://fidoalliance.org/specs/fido-v2.0-rd-20170927/fido-client-to-authenticator-protocol-v2.0-rd-20170927.html",
"status": "FIDO Alliance Review Draft"
"href": "https://fidoalliance.org/specs/fido-v2.0-ps-20170927/fido-client-to-authenticator-protocol-v2.0-ps-20170927.html",
"status": "FIDO Alliance Proposed Standard"
},

"FIDO-UAF-AUTHNR-CMDS": {
Expand Down

0 comments on commit 7be2d3d

Please sign in to comment.