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 [thread overview]
Message-ID: <9FDC0B7C-4608-4392-93F9-07D2B4F716F6@ipfire.org> (raw)
In-Reply-To: <a788eeb7-901c-38fe-6bef-17e3758c6b30@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
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 notice very quickly.
You can submit a patch to enable this in the kernel. Please verify before, obvs.
-Michael
> On 7 Mar 2020, at 09:18, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello *,
>
> while debugging some broken IPsec connections, I stumbled across these log lines:
>
>> 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(chacha20,poly1305)) (seqiv(rfc7539esp(chacha20-simd,poly1305-simd)))
>
> Is this something we should care about?
>
> Thanks, and best regards,
> Peter Müller
prev parent reply other threads:[~2020-03-08 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 9:18 Peter Müller
2020-03-08 11:51 ` Michael Tremer [this message]
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=9FDC0B7C-4608-4392-93F9-07D2B4F716F6@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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