| 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
| ||
|
Message-Id: <1257875623.2834.19.camel@achroite.uk.solarflarecom.com> Date: Tue, 10 Nov 2009 17:53:43 +0000 From: Ben Hutchings <bhutchings@...arflare.com> To: Chris Friesen <cfriesen@...tel.com> Cc: netdev@...r.kernel.org, Linux kernel <linux-kernel@...r.kernel.org> Subject: Re: sunrpc port allocation and IANA reserved list On Tue, 2009-11-10 at 11:43 -0600, Chris Friesen wrote: > By default sunrpc ports are allocated at random in the range 665-1023U. > However, there are many ports within this range which have been > reserved by the IANA (and others like port 921 which are not formally > reserved but are "well-known"). > > Given that a userspace application can be stopped and restarted at any > time, and a sunrpc registration can happen at any time, what is the > expected mechanism to prevent the kernel from allocating a port for use > by sunrpc that reserved or well-known? > > Apparently Redhat and Debian have distro-specific ways of dealing with > this, but is there a standard solution? Should there be? > > The current setup seems suboptimal. I believe both RH and Debian are using the same implementation: <http://cyberelk.net/tim/software/portreserve/>. Ben. -- Ben Hutchings, Senior Software Engineer, Solarflare Communications Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists