• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle









  • I don’t understand why you think it’s either/or? I didn’t say, “Starbucks is solely to blame” or anything of the sort. It’s incredibly stupid that living requires an employer, and that’s something we need to fix, but as long as it does they should act and be treated like they have the ethical responsibility they’ve been given.

    Maybe you should stop giving people free passes for psychopathy just because it’s within the law.


  • To the company it is “an adjustment.” To those people, it can be a devastating loss of healthcare, of the money they use to pay for food and shelter, and even an identity crisis. Starbucks has all sorts of positions, ranging from seasonal part time employees, to store management that gets paid pretty well, to corporate employees that presumed they were in 20y career trajectories. Every single one of them deserves better than losing their job just to pay for a big bonus for one guy.

    It’s not about whether they are allowed or not. It’s that actions should have consequences but the modern corporate structure has so divorced leadership from the consequence of their actions that this is normal. Let me rephrase: Hurting people to pump your personal wealth is not just normal, it’s expected. That’s sick.


  • The other poster gave you a lot. If that’s too much at once, the really low hanging fruit you want to start with is:

    • Choose an active, secure distro. There’s a lot of flavors of Linux out there and they can be fun to try but if you’re putting something up publicly it should be running on one that’s well maintained and known for security. CentOS and Debian are excellent easy choices for example.

    • Similarly, pick well maintained software with a track record. Nginx and Apache have been around forever and have excellent track records, for example, both for being secure and fixing flaws quickly.

    • If you use Docker, once again keep an eye out for things that are actively maintained. If you decide to use Nginx, there will be five million containers to choose from. DockerHub gives you the tools to make this determination: Download number is a decent proxy for “how many people are using this” and the list of updates tells you how often and how recently it’s being updated.

    • Finally, definitely do look at the other poster’s notes about SSH. 5 seconds after you put up an SSH server, you’ll be getting hit with rogue login attempts.

    • Definitely get a password manager, and it’s not just one password per server but one password per service. Your login password to the computer is different from your login to any other things your server is running.

    The rest requires research, but these steps will protect you from the most common threats pretty effectively. The world is full of bots poking at every service they can find, so keeping them out is crucial. You won’t be protected from a dedicated, knowledgeable attacker until you do the rest of what the other poster said, and then some, so try not to make too many enemies.