From: Chuck Lever <chuck.lever@oracle.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: NFSv3 list <linux-nfs@vger.kernel.org>
Subject: Re: RFC: Is SM_SIMU_CRASH (in rpc.statd) needed?
Date: Tue, 22 Jun 2010 12:58:24 -0400 [thread overview]
Message-ID: <4C20EBB0.9010800@oracle.com> (raw)
In-Reply-To: <4C20E5D7.80908-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
On 06/22/10 12:33 PM, Steve Dickson wrote:
>
>
> On 06/22/2010 10:34 AM, Chuck Lever wrote:
>>> Does anybody know who uses SM_SIMU_CRASH and is it
>>> still needed? I'm getting some push back from our
>>> security folks to plug this DoS hole up...
>>
>> How is it a DoS? statd ignores any SM_SIMU_CRASH from a non-loopback
>> address that does not use a privileged port. To invoke it, you
>> basically have to be a privileged local user.
> It happens during an ISS scan....
What were the exact results?
>> Right now, no one uses it, but I think we should reserve the right to
>> use it in the future. This could be part of a more robust interface
>> between lockd and statd.
> hmm... how can having a way of bringing down a daemon, make it more robust?
SM_SIMU_CRASH is not supposed to bring down statd, it's supposed to
trigger sm-notify. If something else is happening, that's a bug.
next prev parent reply other threads:[~2010-06-22 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 14:34 RFC: Is SM_SIMU_CRASH (in rpc.statd) needed? Chuck Lever
2010-06-22 16:33 ` Steve Dickson
[not found] ` <4C20E5D7.80908-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-06-22 16:58 ` Chuck Lever [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-22 10:03 Steve Dickson
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=4C20EBB0.9010800@oracle.com \
--to=chuck.lever@oracle.com \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/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.