• 0 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle













  • So the error is because a service is already running on port 80 (http). This could be nginx or apache depending on configuration. Nginx is very useful if you plan to run more than one service in the container. And it’s more trusted security wise than I would trust Lemmy right now tbh. I would maybe configure Lemmy to run on a different port locally, and setup an nginx site to proxy to port 80.

    It’s been a while since I’ve messed with devops stuff though, so I may be misremembering a bit.



  • Drive encryption doesn’t really matter to malware, since the disk must be decrypted to function when turned on. Also the majority of malware still runs in userland, maybe arguably more since the rise of ransomware.

    I’m not sure what you mean by permissions being limited to the Microsoft store exactly, but there’s a very robust permissions system built into Windows by default. It’s just not very user friendly, and your average user wouldn’t know it exists probably.

    There’s arguments on both sides about default security policies anyway, as I’ve found navigating osx systems to install software can often be a nightmare - but that could be due to my lack of experience with it directly.

    Both systems have pros and cons from a security standpoint. In the corporate spaces I’ve worked in, osx security is more annoying to manage from a central point than Windows.




  • I live alone. So I just have reserved IPs for each of my devices. Any new device gets assigned >200 so that I can easily identify new stuff, or rogue devices - which hasn’t happened lol. The only special IP is my pihole that gets 192.168.1.2 next to my router since I consider it infrastructure basically. Plus pihole is my dhcp server and dns obviously


  • I’m sure I’ve committed many code crimes. But the one that should send someone to jail that I’ve personally seen was when I found an eval in production code that was actively being exploited. Put up a PR to fix it and was given a very hush hush meeting that it was there intentionally to fix production data issues secretly because the bureaucracy made it hard to do lol. I just kept my mouth shut and eventually used it once myself.