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

Blake 256 and 512 #18

Open
GoogleCodeExporter opened this issue Aug 27, 2015 · 4 comments
Open

Blake 256 and 512 #18

GoogleCodeExporter opened this issue Aug 27, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

This is a request, not an issue.  Is there a chance that we could have the 
Blake-256 and Blake-512 hashing algoritms added to this library?  Thank you.

Original issue reported on code.google.com by rhartn...@gmail.com on 29 Nov 2011 at 4:51

@GoogleCodeExporter
Copy link
Author

Original comment by Jeff.Mott.OR on 3 Dec 2011 at 8:45

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Let's wait and see what comes out of the SHA3 competition. If BLAKE is chosen, 
then it will definitely be implemented.

Original comment by Jeff.Mott.OR on 7 Jan 2012 at 11:10

@GoogleCodeExporter
Copy link
Author

hi dear

I am very new to this field basically i am from networking backgroung but your 
project sound interesting and want to join you.. please let me know how to 
implement your codes  in to my own projects. mail me ar 
ranjan9910349038@gmail.com

Original comment by Ranjan99...@gmail.com on 17 Apr 2012 at 9:35

@GoogleCodeExporter
Copy link
Author

I think we should still have Blake and a few other SHA3 finalists as part of 
the libary. NIST (NSA) have been tweaking Keccak for the SHA3 standard and 
opting for a weaker subset of it. Implementers of protocols can choose which 
hash functions they really want.

Original comment by john.f.m...@gmail.com on 28 Jan 2014 at 5:14

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