From: David Ahern <dsahern@gmail.com>
To: Magali Lemes <magali.lemes@canonical.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org
Cc: andrei.gherzan@canonical.com, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 2/3] selftests: net: vrf-xfrm-tests: change authentication and encryption algos
Date: Wed, 7 Jun 2023 12:35:01 -0600 [thread overview]
Message-ID: <8df72efd-334a-40b6-7d4c-62c8e5a36fc0@gmail.com> (raw)
In-Reply-To: <20230607174302.19542-3-magali.lemes@canonical.com>
On 6/7/23 11:43 AM, Magali Lemes wrote:
> The vrf-xfrm-tests tests use the hmac(md5) and cbc(des3_ede)
> algorithms for performing authentication and encryption, respectively.
> This causes the tests to fail when fips=1 is set, since these algorithms
> are not allowed in FIPS mode. Therefore, switch from hmac(md5) and
> cbc(des3_ede) to hmac(sha1) and cbc(aes), which are FIPS compliant.
>
> Fixes: 3f251d741150 ("selftests: Add tests for vrf and xfrms")
> Signed-off-by: Magali Lemes <magali.lemes@canonical.com>
> ---
> tools/testing/selftests/net/vrf-xfrm-tests.sh | 32 +++++++++----------
> 1 file changed, 16 insertions(+), 16 deletions(-)
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2023-06-07 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 17:42 [PATCH net 0/3] Check if FIPS mode is enabled when running selftests Magali Lemes
2023-06-07 17:43 ` [PATCH net 1/3] selftests: net: tls: check if FIPS mode is enabled Magali Lemes
2023-06-09 2:17 ` Jakub Kicinski
2023-06-07 17:43 ` [PATCH net 2/3] selftests: net: vrf-xfrm-tests: change authentication and encryption algos Magali Lemes
2023-06-07 18:35 ` David Ahern [this message]
2023-06-07 17:43 ` [PATCH net 3/3] selftests: net: fcnal-test: check if FIPS mode is enabled Magali Lemes
2023-06-07 18:35 ` David Ahern
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=8df72efd-334a-40b6-7d4c-62c8e5a36fc0@gmail.com \
--to=dsahern@gmail.com \
--cc=andrei.gherzan@canonical.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=magali.lemes@canonical.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).