netdev - Re: [PATCH net-next 1/2] ipv4: move local_port_range out of CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAM_iQpUGvKegVSUtg4uD9F08TEqrSYOgdhCrp_XFq9DYc=-8=A@mail.gmail.com>
Date:	Thu, 8 May 2014 22:17:46 -0700
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	Francois Romieu <romieu@...zoreil.com>,
	Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next 1/2] ipv4: move local_port_range out of CONFIG_SYSCTL

On Thu, May 8, 2014 at 7:52 PM, David Miller <davem@...emloft.net> wrote:
> From: Francois Romieu <romieu@...zoreil.com>
> Date: Thu, 8 May 2014 00:48:48 +0200
>
>> David Miller <davem@...emloft.net> :
>> [...]
>>> I think these two changes fix fairly serious issues that have existed for some
>>> time, so it should go into 'net', do you agree?
>>
>> Patch #1, yes.
>>
>> Without patch #2, the root group id is always granted ping init when
>> CONFIG_SYSCTL is not set. It's more cautious than serious.
>
> Still, initializing such fundamental values to different defaults
> based upon whether SYSCTL is enabled or not is pretty bad, so I've
> decided to apply both patches to 'net'.
>

Makes sense for me. Thanks, everyone!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html