| 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: <76bd70e30609010908n47eb356ob121109961f8221c@mail.gmail.com> Date: Fri, 1 Sep 2006 12:08:14 -0400 From: "Chuck Lever" <chucklever@...il.com> To: "Olaf Kirch" <okir@...e.de> Cc: NeilBrown <neilb@...e.de>, "Andrew Morton" <akpm@...l.org>, nfs@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: [NFS] [PATCH 019 of 19] knfsd: Register all RPC programs with portmapper by default On 9/1/06, Olaf Kirch <okir@...e.de> wrote: > On Fri, Sep 01, 2006 at 11:31:25AM -0400, Chuck Lever wrote: > > I don't like this. The idea that multiple RPC services are listening > > on the same port is a total hack. What other service might use this > > besides NFSACL? > > Why do you consider this a hack? I have always felt that librpc requiring > you to open separate ports for every program you register was a poor > design. The RPC header contains the program number, and the RPC code > is fully capable of demuxing incoming requests. So I do not think it is > a hack at all. > > And yes, Solaris NFSACL resides on 2049 too. I meant "Does Solaris advertise NFSACL on 2049 via the portmapper?" -- "We who cut mere stones must always be envisioning cathedrals" -- Quarry worker's creed - 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