From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [NFS] [PATCH 0/3] NLM lock failover
Date: Fri, 04 Aug 2006 09:27:59 -0400 [thread overview]
Message-ID: <1154698079.3378.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1154683665.21040.2431.camel@hole.melbourne.sgi.com>
On Fri, 2006-08-04 at 19:27 +1000, Greg Banks wrote:
> On Tue, 2006-08-01 at 11:55, Wendy Cheng wrote:
> > o The nfs-utils config flag RESTRICTED_STATD must be off for NLM
> > failover to be functional correctly.
>
> That would reopen this ancient security hole:
>
> http://www.cert.org/advisories/CA-99-05-statd-automountd.html
>
> which might not be the best of ideas.
>
ok, thanks ! I'll look into this. But I believe nfs-utils-1.0.8-rc4 has
this off by default ?
-- Wendy
WARNING: multiple messages have this Message-ID (diff)
From: Wendy Cheng <wcheng@redhat.com>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: cluster-devel@redhat.com, lhh@redhat.com,
Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: [PATCH 0/3] NLM lock failover
Date: Fri, 04 Aug 2006 09:27:59 -0400 [thread overview]
Message-ID: <1154698079.3378.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1154683665.21040.2431.camel@hole.melbourne.sgi.com>
On Fri, 2006-08-04 at 19:27 +1000, Greg Banks wrote:
> On Tue, 2006-08-01 at 11:55, Wendy Cheng wrote:
> > o The nfs-utils config flag RESTRICTED_STATD must be off for NLM
> > failover to be functional correctly.
>
> That would reopen this ancient security hole:
>
> http://www.cert.org/advisories/CA-99-05-statd-automountd.html
>
> which might not be the best of ideas.
>
ok, thanks ! I'll look into this. But I believe nfs-utils-1.0.8-rc4 has
this off by default ?
-- Wendy
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-08-04 13:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 17:47 [Cluster-devel] [RFC PATCH 0/3] NLM lock failover Wendy Cheng
2006-06-29 17:47 ` Wendy Cheng
2006-08-01 1:55 ` [Cluster-devel] [PATCH " Wendy Cheng
2006-08-01 1:55 ` Wendy Cheng
[not found] ` <message from Wendy Cheng on Monday July 31>
2006-08-03 4:14 ` [Cluster-devel] Re: [NFS] " Neil Brown
2006-08-03 4:14 ` Neil Brown
2006-08-03 21:34 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2006-08-07 22:38 ` Wendy Cheng
2006-08-04 9:27 ` Greg Banks
2006-08-04 9:27 ` Greg Banks
2006-08-04 13:27 ` Wendy Cheng [this message]
2006-08-04 13:27 ` Wendy Cheng
2006-08-04 14:56 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2006-08-04 14:56 ` Wendy Cheng
2006-08-04 15:51 ` [Cluster-devel] Re: [NFS] " Trond Myklebust
2006-08-04 15:51 ` Trond Myklebust
2006-08-05 5:44 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2006-08-05 5:44 ` Wendy Cheng
2006-08-07 4:05 ` [Cluster-devel] Re: [NFS] " Greg Banks
2006-08-07 4:05 ` Greg Banks
2006-08-07 20:14 ` [Cluster-devel] Re: [NFS] " James Yarbrough
2006-08-07 20:14 ` James Yarbrough
2006-08-07 21:03 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2006-08-07 4:05 ` Greg Banks
2006-08-07 4:05 ` Greg Banks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1154698079.3378.2.camel@localhost.localdomain \
--to=wcheng@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.