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] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200821.143553.1454267475258459257.davem@davemloft.net>
Date:   Fri, 21 Aug 2020 14:35:53 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     maze@...gle.com
Cc:     maheshb@...gle.com, netdev@...r.kernel.org, kuba@...nel.org,
        edumazet@...gle.com, mahesh@...dewar.net, jianyang@...gle.com
Subject: Re: [PATCH next] net: add option to not create fall-back tunnels
 in root-ns as well

From: Maciej Żenczykowski <maze@...gle.com>
Date: Fri, 21 Aug 2020 14:25:20 -0700

> If no kernel command line option is specified, should the default
> be to maintain compatibility, or do you think it's okay to make
> the default be no extra interfaces?  They can AFAICT always be added
> manually via 'ip link add' netlink commands.

You can't change current default behavior, so the answer should be
obvious right?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ