From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Kernel bugs
Date: Mon, 29 Mar 2021 21:19:12 +0100 [thread overview]
Message-ID: <3013398E-ABB4-4BDF-9FEA-12070CD60B6E@ipfire.org> (raw)
In-Reply-To: <e21ebd60-2193-0dd7-d8d9-75d559386d91@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
Hello,
Unfortunately this is a bit of a click-bait article with bad advice at the end.
However, they should be included in Arne’s next kernel release.
-Michael
> On 27 Mar 2021, at 21:47, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi All,
>
> I suspect this is already known about but just in case not I am highlighting on the list.
>
> https://nakedsecurity.sophos.com/2021/03/17/serious-security-the-linux-kernel-bugs-that-surfaced-after-15-years/
>
>
> Regards,
>
> Adolf
>
prev parent reply other threads:[~2021-03-29 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 21:47 Adolf Belka
2021-03-29 20:19 ` 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=3013398E-ABB4-4BDF-9FEA-12070CD60B6E@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