From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Neil Brown <neilb@suse.de>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: RESTRICTED_STATD
Date: Wed, 27 Aug 2008 06:57:47 -0400 [thread overview]
Message-ID: <48B5332B.2040800@RedHat.com> (raw)
In-Reply-To: <6972A199-D332-4E74-9D47-70EC2CA381FE@oracle.com>
Chuck Lever wrote:
> Hi guys-
>
> I was wondering if anyone ever builds nfs-utils with RESTRICTED_STATD
> undefined these days. It seems totally insecure to do. Is it still
> necessary to keep this?
>
> It would be easier to understand, update, and test the logic in
> utils/statd/monitor.c (IPv6-wise) if we could remove the unused parts of
> this code.
>
> I propose removing RESTRICTED_STATD, leaving in the secure version of
> the code permanently and removing the insecure parts that are left out
> when RESTRICTED_STATD is undefined.
>
> Thoughts?
I seem to remember enabling RESTRICTED_STATD cause problems with
portmapper and kernel interactions which causes me to turn it off...
So if we do permanently turn on the code, let make sure lock recover
and such still work...
steved.
next prev parent reply other threads:[~2008-08-27 11:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 20:41 RESTRICTED_STATD Chuck Lever
2008-08-26 21:08 ` RESTRICTED_STATD NeilBrown
2008-08-27 10:57 ` Steve Dickson [this message]
[not found] ` <48B5332B.2040800-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-08-27 14:14 ` RESTRICTED_STATD Chuck Lever
[not found] ` <76bd70e30808270714p4342c8c3k8d1b98763cc95aef-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-29 20:56 ` RESTRICTED_STATD Chuck Lever
2008-08-29 21:31 ` RESTRICTED_STATD NeilBrown
[not found] ` <3400963b9465552abb83ecefede125bc.squirrel-eq65iwfR9nKIECXXMXunQA@public.gmane.org>
2008-09-02 22:17 ` RESTRICTED_STATD Chuck Lever
2008-09-04 6:03 ` RESTRICTED_STATD Neil Brown
[not found] ` <18623.31268.970805.5694-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-09-04 7:38 ` RESTRICTED_STATD Olaf Kirch
2008-09-04 15:51 ` RESTRICTED_STATD Chuck Lever
2008-09-05 1:26 ` RESTRICTED_STATD Neil Brown
[not found] ` <18624.35551.98462.115701-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-09-05 1:59 ` RESTRICTED_STATD Chuck Lever
2008-09-05 6:56 ` RESTRICTED_STATD Olaf Kirch
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=48B5332B.2040800@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox