Skip to content
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

Which of the attestation format interfaces are expected to be exposed in UAs? #287

Closed
bzbarsky opened this issue Nov 4, 2016 · 1 comment
Milestone

Comments

@bzbarsky
Copy link

bzbarsky commented Nov 4, 2016

Does a UA conforming to this specification expose all the attestation format interfaces (as properties on the global) even though it may never return any instances of them? Does it only expose the ones it might return instances of? Are both behaviors OK? This is not clear from the spec.

@equalsJeffH equalsJeffH added this to the WD-04 milestone Nov 7, 2016
@vijaybh
Copy link
Contributor

vijaybh commented Nov 7, 2016

This should be addressed by #244 which aims to make attestation an ArrayBuffer.

vijaybh added a commit that referenced this issue Jan 11, 2017
Fixed small wording and markdown issues. This completes the changes to
make attestation opaque to UAs, which fixes #286, fixes #287, and fixes
#289. It also fixes #239 by removing the homegrown algorithm identifiers
and specifying the algorithm explicitly in attestation data using JWK
identifiers. It also fixes #240 by encoding keys in CBOR which specifies
lengths of fields.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants