| 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
| ||
|
Date: Thu, 04 Feb 2010 15:31:22 +0100 From: Patrick McHardy <kaber@...sh.net> To: Jan Engelhardt <jengelh@...ozas.de> CC: Thomas Woerner <twoerner@...hat.com>, netdev@...r.kernel.org, Netfilter Developer Mailing List <netfilter-devel@...r.kernel.org> Subject: Re: netfilter/iptables and network interface names Jan Engelhardt wrote: > On Thursday 2010-02-04 13:58, Thomas Woerner wrote: > >> Hello, >> >> I just fell over network interface definitions in kernel and >> netfilter/iptables. >> >> Interfaces names in the kernel have few limits: Only spaces and slashes are not >> allowed, but everything else, even Ctrl characters are. >> >> In iptables, there are other limits: Colon, exclamation mark and asterisk are >> not allowed. The plus is treated special for matching. But what will be matched >> if the interface starts with or contains a plus? >> >> iptables allows to use interfaces containing spaces and slashes. iptables-save >> is not escaping interface names. The interface "+" will be treated as no >> interface limit at all and will be dropped, therefore all interfaces match. >> >> I think there should be some discussion about interface names and limits in >> kernel and netfilter/iptables. >> >> What do you think? > > I think we should cc netdev for a start. I don't think there is a reason for this limitation in iptables, so why not simply remove it? -- 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
Powered by blists - more mailing lists