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

section {#uvm-extension} cites FIDO registry w/o proper references #200

Closed
equalsJeffH opened this issue Sep 15, 2016 · 0 comments
Closed
Assignees
Milestone

Comments

@equalsJeffH
Copy link
Contributor

[ hat tip: Yaron Sheffer ]

For the cites below of "FIDO Registry of Predefined Values"..

    Each data item is in turn a CBOR array of length 3 (type 0x83) with the following data items:
    - Data Item 1 – User Verification Method. This is the authentication method/factor used by the authenticator to verify 
                    the user. Available values are defined in the FIDO Registry of Predefined Values, ‘User Verification 
                    Methods’ section. It is encoded as a CBOR unsigned integer (Major type 0).
    - Data Item 2 – Key Protection Type. This is the method used by the authenticator to protect the FIDO registration 
                    private key material. Available values are defined in the FIDO Registry of Predefined Values, ‘Key 
                    Protection Types’ section. It is encoded as a CBOR 2 byte unsigned short (Major type 0).
    - Data Item 3 – Matcher Protection Type. This is the method used by the authenticator to protect the matcher that 
            performs user verification. Available values are defined in the FIDO Registry of Predefined Values, 
            ‘Matcher Protection Types’ section. It is encoded as a CBOR 2 byte unsigned short (Major type 0).

..we "Just" (he says) need to cite the proper reference. Presently, the publicly published version is here..

https://fidoalliance.org/specs/fido-uaf-v1.0-ps-20141208/fido-uaf-reg-v1.0-ps-20141208.html

It may be updated/revised in the next several months. If so, the present values within it will not change, only additions will be made.

@equalsJeffH equalsJeffH added this to the WD-02 milestone Sep 15, 2016
@equalsJeffH equalsJeffH self-assigned this Sep 15, 2016
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

1 participant