Skip to contentSkip to conversation

RFC: Is SM_SIMU_CRASH (in rpc.statd) needed?

DISCUSSION Chuck Lever 2 participants 3 messages Jun 22, 2010 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore raw
Quoted 3 lines

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.

Signature · 1 line
Chuck Lever
#1 lore raw
Quoted 7 lines · Chuck Lever
Quoted 3 lines

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....

Quoted 4 lines

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.

#3 lore raw
In reply to a message not in the archive
Quoted 11 lines · Steve Dickson
Quoted 7 lines · Chuck Lever
Quoted 3 lines

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?

Quoted 4 lines
Quoted 3 lines

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.