* RFC: Is SM_SIMU_CRASH (in rpc.statd) needed?
@ 2010-06-22 10:03 Steve Dickson
0 siblings, 0 replies; 4+ messages in thread
From: Steve Dickson @ 2010-06-22 10:03 UTC (permalink / raw)
To: Linux NFS Mailing list
Hello,
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...
steved.
^ permalink raw reply [flat|nested] 4+ messages in thread
* RFC: Is SM_SIMU_CRASH (in rpc.statd) needed?
@ 2010-06-22 14:34 Chuck Lever
2010-06-22 16:33 ` Steve Dickson
0 siblings, 1 reply; 4+ messages in thread
From: Chuck Lever @ 2010-06-22 14:34 UTC (permalink / raw)
To: Steve Dickson, NFSv3 list
> 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.
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.
--
Chuck Lever
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: RFC: Is SM_SIMU_CRASH (in rpc.statd) needed?
2010-06-22 14:34 Chuck Lever
@ 2010-06-22 16:33 ` Steve Dickson
[not found] ` <4C20E5D7.80908-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
0 siblings, 1 reply; 4+ messages in thread
From: Steve Dickson @ 2010-06-22 16:33 UTC (permalink / raw)
To: Chuck Lever; +Cc: NFSv3 list
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....
>
> 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?
steved.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: RFC: Is SM_SIMU_CRASH (in rpc.statd) needed?
[not found] ` <4C20E5D7.80908-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
@ 2010-06-22 16:58 ` Chuck Lever
0 siblings, 0 replies; 4+ messages in thread
From: Chuck Lever @ 2010-06-22 16:58 UTC (permalink / raw)
To: Steve Dickson; +Cc: NFSv3 list
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-06-22 17:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-06-22 10:03 RFC: Is SM_SIMU_CRASH (in rpc.statd) needed? Steve Dickson
-- strict thread matches above, loose matches on Subject: below --
2010-06-22 14:34 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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).