alienscience

joined 2 years ago
[โ€“] [email protected] 3 points 1 day ago (2 children)

I do this for sites where I don't care at all about security. One minor tip, that will protect against automated attacks if the password is cracked, is to add part of the website name into the password (e.g "mystrongp4ss!lemworld") .

A human could easily crack it, but automated systems that replay the password on different sites would probably not bother to calculate the pattern.

[โ€“] [email protected] 4 points 1 day ago (2 children)

I also use KeepassXC and Synthing together and I am very happy with this combination.

One tip that I have, if you are worried about the security of the database file being shared, is to get 2 Yubikeys and use these, along with a strong passphrase, to protect the database file.

 

I installed K3s for some hobby projects over the weekend and, so far, I have been very impressed with it.

This got me thinking, that it could be a nice cheap alternative to setting up an EKS cluster on AWS -- something I found to be both expensive and painful for the availability that we needed.

Is anybody using K3s in production? Is it OK under load? How have upgrades and compatibility been?