NPM allows for code to be executed while you install the package which is different from maven or nuget and allows for easy exploitation paths

This is the winner. Combine that with a vastly bigger group of inexperienced developers (and I’m willing to die on that hill), and you have a lot of people running node / npm as an admin / root user, who have close to zero idea what they are doing, hitting their project with third party dependencies left and right for no particular reason (left-pad, is-number, ansi console and similar useless crap), and then your dependency management allows for code execution. Also, from my personal feeling, it seems that npm simply cannot properly audit the packages due to the sheer mass. From a technical standpoint it’s close to trivial to put your malware onto npm, and then you just need to get someone to install your package, which is way simpler than in other package managers

Right, completely forgot that locking exists in SVN, and I guess it definitely makes sense if you’re collaboratively editing unmergeable files.

Thanks!

Serious question, why do they use SVN, as in what does SVN better than Git for the department using it?

So, the “license to kill” is fine, as long it’s non US citizens?

Your definition of democracy and basic human rights is fucking unhinged.

Neat, thank you for the hint - only recently got a ccwgtv, and I’m still not used to the fact that you’re able to install apps like this 😂

Same for me on Chromecast, it’s pretty much unwatchable overnight, started probably about a week ago. I’m to lazy to set up adblocking for my full network, and I was fine watching the skippable 15s ads, and the occasional longer ones, but currently I mostly get at least a full minute of ads on my TV.

You’re right, containers are not VMs, and I’ve never claimed that. For the matter of basic unix access control for a beginner they are similar enough to treat them as such. It’s enough of a baseline for basic security for a beginners workload imo. For advanced use cases - absolutely do not treat containers as you would VMs.

Imagine your containers as very lightweight mini-VMs. Would you run everything as root in your virtual machines? Containers aren’t really that different to classical VMs from an operations point of view. You have a different attack surface, but it is still there, and running as a non-root user inside the container reduces this attack surface, and should IMHO be the default. Privileged containers and users may be required for specific purposes, but should not be the norm, if possible.

Yeah, that’s literally the same as 12ft or any other anti paywall tool. I mean hey, it’s just two lines, that’s even 8 less than the original smoothbrain, absolutely easy to use for any end user. Thanks. /s

And who’s gonna maintain the fork? Even less developers from a split community? You have absolutely no idea what you’re talking about.