• 0 Posts
  • 70 Comments
Joined 1 year ago
cake
Cake day: June 29th, 2023

help-circle






  • gencha@lemm.eetoLinux@lemmy.mlMy latest Linux-convincing story
    link
    fedilink
    arrow-up
    47
    arrow-down
    1
    ·
    1 month ago

    How do you sell what you did as “it just worked”? Rightaway? You lied to them. You have your coworkers on an unmanaged machine with a foreign OS on the guest WiFi with custom networking. Don’t oversell a workaround as a solution.

    Simplifying the problem to “Windows” seems unfair, given how many problems you found. All of them still require a long-term solution for regular operation.







  • I don’t even disagree with you. However…

    There are thousands of people at home with access to privileged information and they have never heard of a KVM switch. It’s insane how blind to reality some people here are. If you have never been in an online meeting where a participant had their camera off, mic on, was AFK, and their child fucked around on the laptop, because they never lock it, then you really have no fucking idea about security at scale.

    Just because some people here love to work from home, doesn’t mean it applies to an entire corporation as large as Amazon




  • So how did those laptops get stolen? Would that have been possible if their users worked on a local client at the office?

    Rocket science is a fucking joke compared to secure IT practices. You saying that, proves that you know neither well enough to participate in this discourse. Most users would operate more securely if their client device was also physically restricted. If you don’t understand that, that’s the reason you are not making decisions. I’m sorry to be so blunt.

    There are highly capable technical people that can securely work from home, but this is not the average user. If you don’t recognize that, you are probably just cheering for your own personal comfort right now. I get comfort, but don’t be blind to reality


  • Just because you can perform a job from home, doesn’t mean it’s ideal for performance. With jobs like surgeons or bus drivers it’s more obvious, but the cut is not as clear as people like it to be.

    I would hope it doesn’t take you long to imagine someone who has access to information about you where you would prefer it not be open on their laptop on their kitchen table at home while guests are around.

    I’m not trying to defend Amazon. This is an active subject at many companies.




  • Ultimately, it doesn’t matter what caused you to be blocked from Docker Hub due to rate-limiting. When you’re in that scenario, it’s most cost efficient to buy your way out.

    If you can’t even imagine what would lead up to such a situation, congratulations, because it really sucks.

    Yes, there should be a cache. But sometimes people force pull images on service start, to ensure they get the latest “latest” tag. Every tag floats, not just “latest”. Lots of people don’t pin digests in their OCI references. This almost implies wanting to refresh cached tags regularly. Especially when you start critical services, you might pull their tag in case it drifted.

    Consider you have multiple hosts in your home lab, all running a good couple services, you roll out that new container runtime upgrade to your network, it resets all caches and restarts all services. Some pulls fail. Some of them are for DNS and other critical services. Suddenly your entire network is down, and you can’t even get on the Internet, because your pihole doesn’t start. You can’t recover, because you’re rate-limited.

    I’ve been there a couple of times until I worked on better resilience, but relying on docker.io is still a problem in general. I did pay them for quite some time.

    This is only one scenario where their service bit me. As a developer, it gets even more unpleasant, and I’m not talking commercial.