You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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).
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 gid1234
). 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.
The text was updated successfully, but these errors were encountered: