Description of problem:
Version-Release number of selected component (if applicable):
How reproducible: always
Steps to Reproduce:
1. Use Nussus vulnerability scanner, may be other applications
2. Start scanning 127.0.0.1 (localhost)
3. If cupsd stopped, the application continues working
4. If cupsd disabled, the application works OK, no problem
This is quite vague -- can you be more specific please?
Does printing still work after you use Nessus?
I have the same problem. Printing stops also. I cannot even kill cupsd with kill
-15, I have to kill it hard with kill -9. All my CUPS instances show this behaviour.
This is a serious security issue. It's very easy to take a CUPS print daemon
down by overloading the WebGui with a scanner like Nessus.
Please provide specific details so that I can analyze this problem properly.
Does this only work from localhost? What messages are written to error_log?
What does 'gdb' say the stack trace is at that point? etc etc etc.
I've upgraded CUPS to 1.1.23 and now it's much more stable and it survives the
Nessus scans. If not, I will update you with the needed information.
But basically: It scanned over the network, so it's not localhost. There are no
messages written to error_log and I've not used gdb for a stack trace.