package/git: prefer OpenSSL SHA-1 and SHA-256 implementation
PATCH 1/1 package/git: prefer OpenSSL SHA-1 and SHA-256 implementation
Git is shipped with its own implementation of SHA-1 and SHA-256. However, when OpenSSL is available (BR2_PACKAGE_OPENSSL=y), it is preferable to leverage the OpenSSL version of these hash algorithm instead. --with-openssl configure flag doesn't enable that, though.
Set OPENSSL_{SHA1,SHA256} make variable when OpenSSL package is selected.
--- package/git/git.mk | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
package/git/git.mk +3 -1
@@ -16,7 +16,9 @@ GIT_DEPENDENCIES = zlib $(TARGET_NLS_DEPENDENCIES) ifeq ($(BR2_PACKAGE_OPENSSL),y) GIT_DEPENDENCIES += host-pkgconf openssl GIT_CONF_OPTS += --with-openssl -GIT_MAKE_OPTS += LIB_4_CRYPTO="`$(PKG_CONFIG_HOST_BINARY) --libs libssl libcrypto`" +GIT_MAKE_OPTS += \ + LIB_4_CRYPTO="`$(PKG_CONFIG_HOST_BINARY) --libs libssl libcrypto`" \ + OPENSSL_SHA1=YesPlease OPENSSL_SHA256=YesPlease else GIT_CONF_OPTS += --without-openssl endif
base-commit: c77c66b7df478f508b8f2affa7a64795504db699
Signature · 6 lines
An old man doll... just what I always wanted! - Clara _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Quoted 11 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Bagas" == Bagas Sanjaya <[email protected]> writes:
Git is shipped with its own implementation of SHA-1 and SHA-256. However, when OpenSSL is available (BR2_PACKAGE_OPENSSL=y), it is preferable to leverage the OpenSSL version of these hash algorithm instead. --with-openssl configure flag doesn't enable that, though.
Set OPENSSL_{SHA1,SHA256} make variable when OpenSSL package is selected.
Signed-off-by Bagas Sanjaya <[email protected]>
What is the added value of doing this? Size? Speed? Why is it not the upstream default?
A quick search for git + OPENSSL_SHA1 lead me to:
https://www.spinics.net/lists/git/msg125401.html
Which is old, but argued for not using the openssl implementation because of performance concerns.
Signature · 5 lines
Bye, Peter Korsgaard _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Hello *,
Quoted 15 lines · Peter Korsgaard
Quoted 11 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Bagas" == Bagas Sanjaya <[email protected]> writes:
Git is shipped with its own implementation of SHA-1 and SHA-256. However, when OpenSSL is available (BR2_PACKAGE_OPENSSL=y), it is preferable to leverage the OpenSSL version of these hash algorithm instead. --with-openssl configure flag doesn't enable that, though.
Set OPENSSL_{SHA1,SHA256} make variable when OpenSSL package is selected.
Signed-off-by Bagas Sanjaya <[email protected]>What is the added value of doing this? Size? Speed? Why is it not the upstream default?
Quoted 7 lines
A quick search for git +
OPENSSL_SHA1lead me to:https://www.spinics.net/lists/git/msg125401.html
Which is old, but argued for not using the openssl implementation because of performance concerns.
Or 'Makefile: make DC_SHA1 the default' ([1]):
Makefile: make DC_SHA1 the default
We used to use the SHA1 implementation from the OpenSSL library by default. As we are trying to be careful against collision attacks after the recent "shattered" announcement, switch the default to encourage people to use DC_SHA1 implementation instead. Those who want to use the implementation from OpenSSL can explicitly ask for it by OPENSSL_SHA1=YesPlease when running "make".
And 'INSTALL: remove discussion of SHA-1 backends' ([2]):
INSTALL: remove discussion of SHA-1 backends
The claim that OpenSSL is the default SHA-1 backend hasn't been true since e6b07da (Makefile: make DC_SHA1 the default, 2017-03-17), but more importantly tweaking the SHA-1 backend isn't something that's common enough to warrant discussing in the INSTALL document, so let's remove this paragraph.
This discussion was originally added in c538d2d (Add some installation notes in INSTALL, 2005-06-17) when tweaking the default backend was more common. The current wording was added in 5beb577 (INSTALL: Describe dependency knobs from Makefile, 2009-09-10).
Regards,
Peter
[1] https://github.com/git/git/commit/e6b07da2780f349c29809bd75d3eca6ad3c35d19
[2] https://github.com/git/git/commit/0ced11d32fea5caec3f014b4e60dd197b9c8aa0f
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Quoted 21 lines · Peter Seiderer
Or '
Makefile: makeDC_SHA1the default' ([1]):
Makefile: makeDC_SHA1the defaultWe used to use the SHA1 implementation from the OpenSSL library by default. As we are trying to be careful against collision attacks after the recent "shattered" announcement, switch the default to encourage people to use
DC_SHA1implementation instead. Those who want to use the implementation from OpenSSL can explicitly ask for it by OPENSSL_SHA1=YesPlease when running "make".And 'INSTALL: remove discussion of SHA-1 backends' ([2]):
INSTALL: remove discussion of SHA-1 backends
The claim that OpenSSL is the default SHA-1 backend hasn't been true since e6b07da (
Makefile: makeDC_SHA1the default, 2017-03-17), but more importantly tweaking the SHA-1 backend isn't something that's common enough to warrant discussing in the INSTALL document, so let's remove this paragraph.
Quoted 6 lines
This discussion was originally added in c538d2d (Add some installation notes in INSTALL, 2005-06-17) when tweaking the default backend was more common. The current wording was added in 5beb577 (INSTALL: Describe dependency knobs from
Makefile, 2009-09-10).
Ah, I didn't see the discussions above before I submitted this patch.
Withdrawn, thanks.
Signature · 6 lines
An old man doll... just what I always wanted! - Clara _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot