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.

Sign up for GitHub

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

Jump to bottom

Clarify how AAGUID is generated to avoid collisions #232

Closed
leshi opened this issue Oct 5, 2016 · 3 comments
Closed

Clarify how AAGUID is generated to avoid collisions #232

leshi opened this issue Oct 5, 2016 · 3 comments
Labels
stat:duplicate

Comments

@leshi
Copy link
Contributor

leshi commented Oct 5, 2016 •
edited
Loading

We may want to specify something about how AAGUIDs are generated so we avoid collisions. Time based? Something else? Here is a helpful RFC: http://www.ietf.org/rfc/rfc4122.txt
@vijaybh
Copy link
Contributor

vijaybh commented Oct 6, 2016

Related to #148 and #149? Can we apply the same resolution - random 16 bytes generated with reasonable entropy?

@equalsJeffH
Copy link
Contributor

Specifically, see section 5 {#authenticator-model}, last paragraph. May we close this issue?

@equalsJeffH
Copy link
Contributor

closing since this is essentially a duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stat:duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@equalsJeffH @leshi @vijaybh