From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/3] libxcrypt: Limit to enabling strong hash algos only
Date: Fri, 30 Jun 2023 15:30:51 +0200 [thread overview]
Message-ID: <20230630133051db39352e@mail.local> (raw)
In-Reply-To: <20230624053223.228117-2-raj.khem@gmail.com>
Hello Khem,
This causes python ptest failures:
{'python3': ['test_crypt', 'test_methods', 'test_sha2_rounds']}
We should probably disable those
On 23/06/2023 22:32:21-0700, Khem Raj wrote:
> This ensures that weak algorithms are not included, which should improve
> the defauls to be more secure
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/recipes-core/libxcrypt/libxcrypt.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/libxcrypt/libxcrypt.inc b/meta/recipes-core/libxcrypt/libxcrypt.inc
> index 997e83fb004..db43a34b11d 100644
> --- a/meta/recipes-core/libxcrypt/libxcrypt.inc
> +++ b/meta/recipes-core/libxcrypt/libxcrypt.inc
> @@ -29,7 +29,7 @@ BUILD_CPPFLAGS = "-I${STAGING_INCDIR_NATIVE}"
> TARGET_CPPFLAGS = "-I${STAGING_DIR_TARGET}${includedir} -Wno-error"
> CPPFLAGS:append:class-nativesdk = " -Wno-error"
>
> -API = "--disable-obsolete-api"
> +API = "--disable-obsolete-api --enable-hashes=strong"
> EXTRA_OECONF += "${API}"
>
> BBCLASSEXTEND = "native nativesdk"
> --
> 2.41.0
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#183356): https://lists.openembedded.org/g/openembedded-core/message/183356
> Mute This Topic: https://lists.openembedded.org/mt/99749300/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-06-30 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 5:32 [PATCH 1/3] mesa: Fix build with upcoming LLVM 17 Khem Raj
2023-06-24 5:32 ` [PATCH 2/3] libxcrypt: Limit to enabling strong hash algos only Khem Raj
2023-06-30 13:30 ` Alexandre Belloni [this message]
2023-07-04 10:54 ` [OE-core] " Ross Burton
2023-07-04 11:01 ` Alexander Kanavin
2023-07-04 16:39 ` Khem Raj
2023-07-05 11:08 ` Ross Burton
2023-07-05 15:56 ` Alexandre Belloni
2023-06-24 5:32 ` [PATCH 3/3] alsa-lib: Disable old API symbols Khem Raj
2023-06-25 6:30 ` [OE-core] [PATCH 1/3] mesa: Fix build with upcoming LLVM 17 Alexander Kanavin
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=20230630133051db39352e@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.