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:	Thu, 10 May 2007 19:45:23 +0300
From:	"Menny Hamburger" <menny@...net.com>
To:	"Trond Myklebust" <trond.myklebust@....uio.no>
Cc:	"Neil Brown" <neilb@...e.de>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] NLM program ID for user space NLM server

Yes, but in our case we don't care. This is a dedicated server where we
don't see any usage for NLM client. We just want to prevent the kernel
from taking the port in case of some accidental NFS mount that ommitted
'nolock'. 

-----Original Message-----
From: Trond Myklebust [mailto:trond.myklebust@....uio.no] 
Sent: Thursday, May 10, 2007 6:27 PM
To: Menny Hamburger
Cc: Neil Brown; linux-kernel@...r.kernel.org
Subject: RE: [PATCH] NLM program ID for user space NLM server

On Thu, 2007-05-10 at 18:30 +0300, Menny Hamburger wrote:
> The idea in the change was to be able to override NLM_PROGRAM with 
> another definition (from our slightly customized build system), so 
> that the kernel never tries to register port 100021.

I repeat: The kernel _NEEDS_ to register RPC service 100021 on the
client so that rpc.statd can find it and notify it of server reboots.

Trond

-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ