netdev - Re: [Patch iproute2] vxlan: use 8472 as default dst port

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]

Date:	Wed, 15 May 2013 14:42:01 -0400
From:	David Stevens <dlstevens@...ibm.com>
To:	Stephen Hemminger <stephen@...workplumber.org>
Cc:	Cong Wang <amwang@...hat.com>, netdev@...r.kernel.org,
	netdev-owner@...r.kernel.org
Subject: Re: [Patch iproute2] vxlan: use 8472 as default dst port

netdev-owner@...r.kernel.org wrote on 05/15/2013 01:48:25 PM:

> From: Stephen Hemminger <stephen@...workplumber.org>
> 
> Sorry, this is a kernel bug.
> Kernel shouldn't bind on module load, needs to do it later when
> device is created. I will fix.

Sorry, didn't see this before last send, and fine, but if
ip changes the port for listens too, then existing users will
still get a new port by default, as soon as they get a new
"iproute2" (instead of as soon as they get a new kernel). But filter
rules and scripts that "know" the old port still won't work -
how is this better than changing the kernel default?

I think in either case, if you care what port it is, you
should specify it explicitly, always. Whether iproute2 or the
kernel makes it different, it'll break (or not) in exactly the same
ways for those who didn't.

                                                +-DLS

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