This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] sha2: new header <sha2.h>
- From: Shawn Landden <shawn at churchofgit dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Mon, 30 Mar 2015 01:15:22 +0000
- Subject: Re: [PATCH] sha2: new header <sha2.h>
- Authentication-results: sourceware.org; auth=none
- References: <1427350202-281697-1-git-send-email-shawn at churchofgit dot com> <20150327194823 dot A4E122C3B11 at topped-with-meat dot com>
On Fri, Mar 27, 2015 at 12:48:23PM -0700, Roland McGrath wrote:
> You haven't said anything to justify the change. People are giving you
> feedback on the implementation details, but that should not be interpreted
> as agreement with the effect of the change. I don't think we have any
> desire whatsoever to support new APIs in -lcrypt. There are other
> libraries that provide things like SHA implementations. Just use those.
I responded to this earlier but it ended up sending an empty message :/
There is alot of duplication of effort on these hash sums and the most commonly used
library for them is OpenSSL, which has infamous licensing issues.
Moreover AFAIK only OpenSSL is mature enough to support Intel and ARM cpu extensions
Although I am not proposing we add support for SHA1 (which is now considered insecure)
I note that git doesn't support Intel or ARM's cpu extensions for SHA1 even though that
application's performance is heavily dependant on hashes.
We already have to do SHA2 hashes in libcrypt, and by adding CPU acceleration support
we can save applications much duplication of effort. OpenSSL is also quite overkill for applications
that do not want to do AES.