From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: kernel: alg: No test for ...
Date: Sun, 08 Mar 2020 11:51:09 +0000
Message-ID: <9FDC0B7C-4608-4392-93F9-07D2B4F716F6@ipfire.org>
In-Reply-To: <a788eeb7-901c-38fe-6bef-17e3758c6b30@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4294497478694312896=="
List-Id: <development.lists.ipfire.org>

--===============4294497478694312896==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,

These are always showing because we have support for these tests disabled in =
the kernel.

I have no idea why we should enable them. If crypto was broken, users would n=
otice very quickly.

You can submit a patch to enable this in the kernel. Please verify before, ob=
vs.

-Michael

> On 7 Mar 2020, at 09:18, Peter M=C3=BCller <peter.mueller(a)ipfire.org> wro=
te:
>=20
> Hello *,
>=20
> while debugging some broken IPsec connections, I stumbled across these log =
lines:
>=20
>> Mar  7 09:55:52 maverick kernel: alg: No test for seqiv(rfc4106(gcm(aes)))=
 (seqiv(rfc4106-gcm-aesni))
>> Mar  7 09:56:14 maverick kernel: alg: No test for seqiv(rfc7539esp(chacha2=
0,poly1305)) (seqiv(rfc7539esp(chacha20-simd,poly1305-simd)))
>=20
> Is this something we should care about?
>=20
> Thanks, and best regards,
> Peter M=C3=BCller


--===============4294497478694312896==--