-
Notifications
You must be signed in to change notification settings - Fork 30
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
Allow developers to use their own crypto schemes #50
Labels
Comments
I think this is also part of #6. |
Close since it is a part of #6 |
So I think there are two parts to this issue, right? One is specifying the scheme in the policy, and the other is actually supplying the scheme to the data structure. I think this issue should remain open to address this second part specifically. |
vqhuy
added a commit
that referenced
this issue
Jun 20, 2017
…eir own hash function. * Convert the default hash function to SHA-512/256 * Part of #50 Credit to KT's team
vqhuy
added a commit
that referenced
this issue
Oct 26, 2017
…eir own hash function. * Convert the default hash function to SHA-512/256 * Part of #50 Credit to KT's team
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As @arlolra commented in #48 (comment):
It also useful to allow the developers to supply theirs own
The text was updated successfully, but these errors were encountered: