Timeline for Invalid users trying to log in to my server
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3, 2012 at 23:52 | comment | added | Kaz |
fail2ban looks cool. I've done that sort of thing with scripts hooked into Apache. It looks like my kind of program.
|
|
| Oct 3, 2012 at 23:47 | comment | added | Kaz | So, if, say, 0.01% of the crackers out there guess my port knock sequence, I don't care. They're not getting in, and the other 99.99% haven't guessed it. That still keeps my syslog cleaner and my machine more quiescent than if I didn't have the knocking. | |
| Oct 3, 2012 at 23:44 | comment | added | Kaz | The argument that port knocking is security by obscurity is sheer twaddle (because it implies that port knocking is security, which it isn't). Although the knock sequence is a sort of password, there is no significant elevation in privilege when it is used. If you obtain the sequence, you have not gained access to anything important, only the ability to talk to a port (something that many servers already leave open). It cannot be compared to a cleartext password that gives you a shell prompt. | |
| Oct 3, 2012 at 23:07 | comment | added | Martin Schröder | Port knocking is security by obscurity. Use ssh keys and fail2ban instead. | |
| Oct 3, 2012 at 21:12 | review | First posts | |||
| Oct 4, 2012 at 6:53 | |||||
| Oct 3, 2012 at 21:08 | history | answered | Kaz | CC BY-SA 3.0 |