netdev - Re: [PATCH v3] net/sctp: Make sha1 as default algorithm if fips is enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Fri, 2 Jun 2023 19:16:09 -0400
From: Xin Long <lucien.xin@...il.com>
To: Simon Horman <simon.horman@...igine.com>
Cc: Ashwin Dayanand Kamat <kashwindayan@...are.com>, Vlad Yasevich <vyasevich@...il.com>, 
	Neil Horman <nhorman@...driver.com>, Marcelo Ricardo Leitner <marcelo.leitner@...il.com>, 
	"David S . Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, 
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, linux-sctp@...r.kernel.org, 
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org, amakhalov@...are.com, 
	vsirnapalli@...are.com, akaher@...are.com, tkundu@...are.com, 
	keerthanak@...are.com
Subject: Re: [PATCH v3] net/sctp: Make sha1 as default algorithm if fips is enabled

On Fri, Jun 2, 2023 at 11:15 AM Simon Horman <simon.horman@...igine.com> wrote:
>
> + Xin Long
>
> On Thu, Jun 01, 2023 at 11:47:54PM +0530, Ashwin Dayanand Kamat wrote:
> > MD5 is not FIPS compliant. But still md5 was used as the
> > default algorithm for sctp if fips was enabled.
> > Due to this, listen() system call in ltp tests was
> > failing for sctp in fips environment, with below error message.
> >
> > [ 6397.892677] sctp: failed to load transform for md5: -2
> >
> > Fix is to not assign md5 as default algorithm for sctp
> > if fips_enabled is true. Instead make sha1 as default algorithm.
> > The issue fixes ltp testcase failure "cve-2018-5803 sctp_big_chunk"
Hi, Ashwin,

I have the same question as Paolo about "this patch gets fips compliance
_disabling_ the encryption", is it from any standard?

If not,  can't you fix the ltp testcase for fips environment by sysctl?
or set 'CONFIG_SCTP_DEFAULT_COOKIE_HMAC_SHA1=y' instead in config.

Sorry if I don't understand this well. You're trying to avoid SCTP code
calling crypto_alloc_shash(MD5), right? What about other places
where it may also do it in kernel? (where ltp just doesn't cover)

I don't think it makes sense to let SCTP have some code reply on
FIPS only to make ltp testcase happy, while we can actually fix it
in ltp by "sysctl".

Thanks.


> >
> > Signed-off-by: Ashwin Dayanand Kamat <kashwindayan@...are.com>
> > ---
> > v3:
> > * Resolved hunk failures.
> > * Changed the ratelimited notice to be more meaningful.
> > * Used ternary condition for if/else condtion.
> > v2:
> > * The listener can still fail if fips mode is enabled after
> >   that the netns is initialized.
> > * Fixed this in sctp_listen_start() as suggested by
> >   Paolo Abeni <pabeni@...hat.com>
>
> FWIIW, this seems reasonable to me.
>
> Reviewed-by: Simon Horman <simon.horman@...igine.com>