On Wed, Aug 29 2018, brian m. carlson wrote:
> Generally, one gets better performance out of cryptographic routines
> written in assembly than C, and this is also true for SHA-256
It makes sense to have a libgcrypt implementation...
> In addition, most Linux distributions cannot distribute Git linked
> against OpenSSL for licensing reasons.
...but I'm curious to know what licensing reasons these are, e.g. Debian
who's usually the most strict about these things distributes git linked
to OpenSSL:
$ dpkg -S /usr/lib/git-core/git-imap-send; apt policy git 2>/dev/null|grep -F '***'; ldd -r /usr/lib/git-core/git-imap-send|grep ssl; uname -m
git: /usr/lib/git-core/git-imap-send
*** 1:2.19.0~rc1+next.20180828-1 1001
libssl.so.1.0.2 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2 (0x00007fd3cc8bb000)
x86_64
$ dpkg -S /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2
libssl1.0.2:amd64: /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2
$ apt show libssl1.0.2 2>&1 |grep ssl
Package: libssl1.0.2
Source: openssl1.0
Maintainer: Debian OpenSSL Team <pkg-openssl-devel@xxxxxxxxxxxxxxxxxxxxxxx>
Homepage: https://www.openssl.org
