Post B6mlIwH7cqQhx3Jxjs by radex@social.hackerspace.pl
 (DIR) More posts by radex@social.hackerspace.pl
 (DIR) Post #B6mlIwH7cqQhx3Jxjs by radex@social.hackerspace.pl
       1 likes, 0 repeats
       
       I find it shocking that in 2026, we’re not religiously sandboxing everything on dev machines. We take so much stuff from the web, with deep dependency trees, and just yolo run it as $USER. It’s a small miracle that most of the time this works out just fine!
       
 (DIR) Post #B6mlIxPJPsZjSkA18y by radex@social.hackerspace.pl
       0 likes, 0 repeats
       
       The silver lining is that most of the so-called supply chain attacks are NOT sophisticated - because they don’t need to be. They usually just smash and grab your ~/.config/{aws,kube,docker,npm,etc…}. So, dumb mitigations (that would have no chance against a targeted attack) have a decent chance of working
       
 (DIR) Post #B6mlQs556T8VGBTIHI by domi@donotsta.re
       0 likes, 0 repeats
       
       @radex i think the reason is how all sandboxing options are virtually unsuitable for development. closest we have is docker, which isn’t sandboxing, and feels downright dreadful to use for development, for me personally
       
 (DIR) Post #B6mrO91qEdLwg92ULo by radex@social.hackerspace.pl
       1 likes, 0 repeats
       
       @domi I agree, but that’s a bit of a chicken-and-egg problem, no? If this was widely considered to be a problem, I’m sure we could come up with better tools to make this less dreadful