netdev - Re: [PATCH 2/2] TCP: Use 32768-65535 outgoing port range by default

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: <20120403.022837.1830755903242379322.davem@davemloft.net>
Date:	Tue, 03 Apr 2012 02:28:37 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	fernando@...ellilink.co.jp
Cc:	shemminger@...tta.com, netdev@...r.kernel.org
Subject: Re: [PATCH 2/2] TCP: Use 32768-65535 outgoing port range by default

From: fernando@...ellilink.co.jp
Date: Tue,  3 Apr 2012 14:18:27 +0900

> The thing is that certain non-linux hosts already use a superset of
> the 61000-65095 range and 61000 looks like a magic number to most
> users.

Who cares what other systems usage, it's only an issue about local
port allocations and locally performed masquerading.

> Do you want me to document where 61000 comes from instead?

I think the current documentation on this is adequate.
--
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