True. Additionally, some might be embarrassed or too afraid to report an incident.

I was concerned that we would now have five competing databases, each with their own, inconsistent data.

I’ve got it running for a few weeks now. Seems very nice

Nice list of suggestions, but implementing all of them feels a little over-the-top.

I don’t really get the love for fail2ban. Sure, it helps keep your logs clean, but with a solid SSH setup (root disabled, SSH keys enforced), I’m not bothered by the login attempts.

The current tariff approach by the republican administration does not include the tariffs on US exports. They are not included in the formula.

Teams randomly selects the wrong microphone, so either people can’t hear me or they can hear everyone around me too (laptop mic).

How hard can it be to store my microphone preference?

This week, I’ve been trying out caddy + coraza web app firewall. I got it to work, I’m planning to use it for my homeserver.

I’m currently comparing Authentik and Authelia. For me, Authentik was extremely easy to get into. Authelia with its text-based configuration is clearly not as easy for beginners.

Dismantle them and build them new inside the bottle probably

With Ivanti VPN, attackers can transfer your data to the darknet over an encrypted connection.

Obvoiusly companies need some data, both for practical and legal requirements.

But tracking every start and stop of a car with 1 meter accuracy meets none of these requirements. This is just a needless risk for everyone involved.

Security by old software, or how I call it: the ivanti approach

Nice new name:

The company now legally known as “THAT COMPANY WHOSE NAME USED TO CONTAIN HTML SCRIPT TAGS LTD”

Not LLMs (Large Language Models). ReCaptcha by Google was used to improve image and text recognition AI.

They’re too special.

I did it both ways, but I wanted to post the more positive version.

Carry a ladder and a toolbox and everyone will open the door for you.

OWASP recommendation is to allow 64 chars at least:

Maximum password length should be at least 64 characters to allow passphrases (NIST SP800-63B). Note that certain implementations of hashing algorithms may cause long password denial of service.

The lemmy-UI limit is reasonably close and as everything is open source, we can verifiy that it does hash the password before storing it in the database.

There is a github issue, too.

Please add kaspersky, symantec, zone alarm and trend micro to make sure you have all the backdoors 100% security.