| 1 |
Joost Roeleveld wrote: |
| 2 |
> On Wednesday 22 June 2011 18:02:39 Alan McKinnon wrote: |
| 3 |
> |
| 4 |
>> But all this was mild compared to what I did yesterday. You know that |
| 5 |
>> notice on the console when you get sudo wrong? It says the incident |
| 6 |
>> "will be reported" |
| 7 |
>> |
| 8 |
>> OK. But to whom? On my shell boxes it gets reported to me. And |
| 9 |
>> yesterday this is what it said: |
| 10 |
>> |
| 11 |
>> <host> : Jun 21 11:55:25 :<user> : 1 incorrect password attempt ; |
| 12 |
>> TTY=pts/194 ; PWD=/some/path ; USER=root ; COMMAND=init 6 |
| 13 |
>> |
| 14 |
>> 500 concurrent sessions on that box is routine, it's a major gateway |
| 15 |
>> server. That poor user has not recovered yet. |
| 16 |
>> |
| 17 |
> You mean, he (or she) will eventually recover? |
| 18 |
> |
| 19 |
> Am curious though, why the attempt for a reboot? |
| 20 |
> |
| 21 |
> |
| 22 |
|
| 23 |
I was curious about that too. I don't use sudo, I'm the only geek in |
| 24 |
the chair here, but I don't think I would want to reboot just because my |
| 25 |
typing was off. |
| 26 |
|
| 27 |
Given what Alan runs and the amount of people it affects, I'm surprised |
| 28 |
it is set up that way. Question. You changed that behavior yet Alan? |
| 29 |
|
| 30 |
Dale |
| 31 |
|
| 32 |
:-) :-) |
Archives