From: Peter Seiderer <ps.report@gmx.net>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
Buildroot <buildroot@buildroot.org>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Matt Weber <matthew.weber@collins.com>
Subject: Re: [Buildroot] [PATCH] package/git: prefer OpenSSL SHA-1 and SHA-256 implementation
Date: Thu, 19 Jan 2023 21:35:38 +0100 [thread overview]
Message-ID: <20230119213538.093a1fa4@gmx.net> (raw)
In-Reply-To: <87cz7aden6.fsf@dell.be.48ers.dk>
Hello *,
On Thu, 19 Jan 2023 11:04:13 +0100, Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>>> "Bagas" == Bagas Sanjaya <bagasdotme@gmail.com> 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 <bagasdotme@gmail.com>
>
> 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.
>
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
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-01-19 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 9:58 [Buildroot] [PATCH] package/git: prefer OpenSSL SHA-1 and SHA-256 implementation Bagas Sanjaya
2023-01-19 10:04 ` Peter Korsgaard
2023-01-19 20:35 ` Peter Seiderer [this message]
2023-01-20 2:35 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230119213538.093a1fa4@gmx.net \
--to=ps.report@gmx.net \
--cc=bagasdotme@gmail.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=matthew.weber@collins.com \
--cc=peter@korsgaard.com \
--cc=yann.morin.1998@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox