netdev - Re: Why is gre0 auto-created, and can we fix it?

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: <20120103.151129.2017623336171898647.davem@davemloft.net>
Date:	Tue, 03 Jan 2012 15:11:29 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	greearb@...delatech.com
Cc:	netdev@...r.kernel.org
Subject: Re: Why is gre0 auto-created, and can we fix it?

From: Ben Greear <greearb@...delatech.com>
Date: Tue, 03 Jan 2012 12:03:56 -0800

> On 01/03/2012 11:59 AM, David Miller wrote:
>> From: Ben Greear<greearb@...delatech.com>
>> Date: Tue, 03 Jan 2012 11:49:50 -0800
>>
>>> As far as I can tell, no other interfaces are auto-created
>>> in this manner.
>>
>> ip6tnl0 and sit0 do it too, just grep for alloc_netdev() under
>> net/{ipv4,ipv6}/
> 
> So, no changing the behaviour?

Probably too risky.  I think the exposure is on the order of ~16
years.

--
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