4 ms·
But it takes CPU, fills up log files, etc. fail2ban is the first thing install. It’s also easy to understand, which I love. It’s basically regex on log files.
by tambourine_man 6y ago
But it takes CPU, fills up log files, etc.
fail2ban is the first thing install. It’s also easy to understand, which I love. It’s basically regex on log files.
- necheffa 6y agoIt really doesn't make that big a difference. I have single core, 515MiB VMs that idle at <1% utilization with background noise. Most distros come with logrotate anyways.
- drdaeman 6y ago> Most distros Most distros those days come with journald, and to best of my awareness journald does not have per-unit (or better, per unit per message type) configurable retention. Still in the TODO list today: https://github.com/systemd/systemd/blob/908dbc70d6abeb9f65624d89fb5ca021815d69ae/TODO#L1037 https://github.com/systemd/systemd/blob/908dbc70d6abeb9f6562... (since at least 2016), with corresponding issue gathering no traction: https://github.com/systemd/systemd/issues/9519 https://github.com/systemd/systemd/issues/9519
- deleted 6y ago[deleted]
- jlgaddis 6y agoYes, but don't most of them also come with syslog forwarding enabled and a syslogd (rsyslog, syslog-ng, etc.) and logrotate installed?
- RL_Quine 6y agoWhat decade are your servers from? A failed key authentication doesn't even involve any cryptographic operation unless they also know the hash of your public key.
- tambourine_man 6y agoRaspberry Pi. It was taking considerable CPU with many attempts per second.
- gramakri 6y agoThere is no cpu use. The hash compare of key will fail if I understand correctly.