This thumbnail is so full of shit I won't be clicking.
I gave WinXP its very own public IPv4 address for an entire month and literally nothing happened. Squeaky clean at the end.
This thumbnail is so full of shit I won't be clicking.
I gave WinXP its very own public IPv4 address for an entire month and literally nothing happened. Squeaky clean at the end.
@teratology
Am I the only person who just isn't bothered by ssh brute force?
Your properly-configured sshd should be accepting only key auth. Let randos try all the passwords they want. There is not one. Everything else is gravy. No root login, fail2ban, different port, port knocking... defense in depth is nice and good practice, but the only attack vectors not covered by "it's key auth only" can only be solved by only allowing ssh from internal address space.
@p
@p @r000t @teratology Heh, for SMTP here I use ssh: sendmail = ssh server_machine sendmail in mutt/gitconfig/…
(btw for the complete idiots that tend to pester me everytime: No I do not use Sendmail, sendmail(1) is a de-facto standard command)
Basically because I'd rather not deal with SASL client certificates, way too close to x509 in most servers (and I'd rather not vendor-lock myself), and then making clients use it sounds like yet another pain.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.