public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Including patch for CVE-2020-25705 into upcoming Core Update 153?
Date: Wed, 18 Nov 2020 19:30:26 +0000	[thread overview]
Message-ID: <97EF20AF-6051-4C72-828E-C6E61C796F02@ipfire.org> (raw)
In-Reply-To: <d317e721d73367fb54ad10608f2fe688@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]

Even better.

Thank you for checking, Arne.

-Michael

> On 18 Nov 2020, at 18:34, Arne Fitzenreiter <arne_f(a)ipfire.org> wrote:
> 
> It is already in kernel since 4.14.203
> 
>    File to patch:
>    Skip this patch? [y]
>    Skipping patch.
>    1 out of 1 hunk ignored
>    patching file net/ipv4/icmp.c
>    Reversed (or previously applied) patch detected!  Skipping patch.
>    2 out of 2 hunks ignored -- saving rejects to file net/ipv4/icmp.c.rej
>    make: *** [linux:137: /usr/src/log/linux-4.14.206-ipfire] Error 1
> 
> 
> 
> 
> Am 2020-11-17 12:05, schrieb Michael Tremer:
>> Hello,
>> Yes, we should add this patch to the currently open next branch.
>> Who will send a patch?
>> Best,
>> -Michael
>>> On 16 Nov 2020, at 16:10, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>> Hello *,
>>> since Core Update 153 is already scheduled to come with a new kernel, including this
>>> patch against CVE-2020-25705 (dubbed "SADDNS" at the time of writing) into it makes
>>> sense IMHO:
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b38e7819cae946e2edf869e604af1e65a5d241c5
>>> Further reading is available at, for example, ZDNet:
>>> https://www.zdnet.com/article/dns-cache-poisoning-poised-for-a-comeback-sad-dns/
>>> Thanks, and best regards,
>>> Peter Müller


      reply	other threads:[~2020-11-18 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 16:10 Peter Müller
2020-11-17 11:05 ` Michael Tremer
2020-11-18 18:34   ` Arne Fitzenreiter
2020-11-18 19:30     ` 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=97EF20AF-6051-4C72-828E-C6E61C796F02@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