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

Combine basename and GPK #92

Open
zanebeckwith opened this issue Nov 8, 2018 · 2 comments
Open

Combine basename and GPK #92

zanebeckwith opened this issue Nov 8, 2018 · 2 comments
Assignees

Comments

@zanebeckwith
Copy link
Collaborator

In the interest of consolidating files that a server or client needs to provide, I propose that we combine the basename and DAA GPK into a single file for input to the tool. This file will conceptually represent the DAA group.

I also propose that this file, by default, be named by the GroupID of the group (e.g. 1234.bin for gid 1234). A new command line flag --gid (for example) could be used to override this default.

This should also be done in our up-coming tool in the ecdaa project.

@drbild
Copy link
Contributor

drbild commented Nov 8, 2018

Is there an existing RFC defining ASN.1 structures for any of this DAA stuff?

@zanebeckwith
Copy link
Collaborator Author

No, not to my knowledge.

There's an RFC for identity-based stuff, from Dan Boneh, from 2007. That discusses encoding of ECC points used in IBE: https://tools.ietf.org/html/rfc5091

Also, the FIDO spec covers similar ground, encoding of curve points.

But those are just for the points, nothing about keys or anything.

The FIDO spec also covers the format for the signatures themselves (and it's just binary concatenation).

Also:
https://crypto.stackexchange.com/questions/48853/prime-extension-field-encoding-asn-1

@zanebeckwith zanebeckwith self-assigned this Nov 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants