All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: lucien.xin@gmail.com
Cc: eric.dumazet@gmail.com, edumazet@google.com,
	netdev@vger.kernel.org, marcelo.leitner@gmail.com,
	sd@queasysnail.net
Subject: Re: [PATCH net 0/2] net: diag: fix a potential security issue
Date: Sat, 21 Oct 2017 12:16:59 +0100 (WEST)	[thread overview]
Message-ID: <20171021.121659.925589637636130294.davem@davemloft.net> (raw)
In-Reply-To: <CADvbK_cLxOGpBwdSX+CkE+HLefT4rjz8tbgrkosGg7f+wmQVTA@mail.gmail.com>

From: Xin Long <lucien.xin@gmail.com>
Date: Sat, 21 Oct 2017 17:45:09 +0800

> Let's just see if David could accept the patches if I will
> remove the "security claim" from changelog, considering
> it as an improvement of sock diag.
> 
> David ?

No I won't.  See my other response.

Use modules.conf or netfilter rules to block "scary networking
protocols" if you are so paranoid about this happening.

Thank you.

  reply	other threads:[~2017-10-21 11:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19  7:32 [PATCH net 0/2] net: diag: fix a potential security issue Xin Long
2017-10-19  7:32 ` [PATCH net 1/2] sock_diag: request _diag module only when the family has been registered Xin Long
2017-10-19  7:32   ` [PATCH net 2/2] inet_diag: request _diag module only when the proto " Xin Long
2017-10-21  1:27 ` [PATCH net 0/2] net: diag: fix a potential security issue David Miller
     [not found]   ` <CADvbK_fWmmC3ggpoT--Pxk3GxZ8Gq_rbdFGTuXk-BuTHTO=eXw@mail.gmail.com>
2017-10-21  6:18     ` Eric Dumazet
2017-10-21  6:51       ` Xin Long
2017-10-21  7:45         ` Eric Dumazet
2017-10-21  8:45           ` Xin Long
2017-10-21  9:45             ` Xin Long
2017-10-21 11:16               ` David Miller [this message]
2017-10-21 11:14     ` David Miller

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=20171021.121659.925589637636130294.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sd@queasysnail.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.