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: <m3fwf9gdjm.fsf@intrepid.localdomain>
Date:	Sat, 21 Jan 2012 18:39:57 +0100
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Ben Greear <greearb@...delatech.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: Why is gre0 auto-created, and can we fix it?

Ben Greear <greearb@...delatech.com> writes:

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

Perhaps making it CONFIGurable would be safe enough, not that I like
CONFIG options for all tiny details (one may argue it's not a tiny
detail).

Haven't looked at the actual code.
-- 
Krzysztof Halasa
--
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