5 ms·

I’ve personally never been hit by a Trojaned Python project, why use any container or jail at all?

kjok 3y ago
It is just a matter of time: https://pytorch.org/blog/compromised-nightly-dependency/ https://pytorch.org/blog/compromised-nightly-dependency/
hifromwork 3y ago
Is this sarcasm? Hard to tell on the internet sometimes. Anyway: * It's scary enough to be hit one time. It's no fun to have one's all passwords, accounts and keys stolen, and sometimes have files encrypted with a ransom demand on top of that. * Ideally we'd like to have a secure-by-default world, where the mere act of installing a dependency or running a helper script doesn't compromise your whole system. We're almost there with our phones, we just need to rethink our desktops too. Of course I don't say you should use containers/sandboxes. It's a tradeoff everyone has to make, but there are many reasons some people (me included) prefer to sandbox everything as much as reasonably possible.
onesphere 3y ago
Shouldn't the OS already do containering with its processes (based on user)? That's kind of the [functional context] approach I take with: https://github.com/matrixApi/encapsule https://github.com/matrixApi/encapsule
- miohtama 3y ago
  Desktop and server operating system do not prevent any process to access file system. Any process can effectively steal any work you have on your file system, and also perform malware attacks by encrypting your files. This is not true for mobile operating systems like Android and iOS where processes cannot know about other processes or access file system.
- insanitybit 3y ago
  The typical User in linux is pretty unconstrained. They can view a lot of global resources, perform arbitrary system calls, view other processes, other users, etc. It's not really a tight sandbox. That's why Linux offers other, more powerful mechanisms for sandboxing such as namespaces, which are the backbone of containers.

kjok 3y ago

It is just a matter of time: https://pytorch.org/blog/compromised-nightly-dependency/ https://pytorch.org/blog/compromised-nightly-dependency/

hifromwork 3y ago

Is this sarcasm? Hard to tell on the internet sometimes. Anyway: * It's scary enough to be hit one time. It's no fun to have one's all passwords, accounts and keys stolen, and sometimes have files encrypted with a ransom demand on top of that. * Ideally we'd like to have a secure-by-default world, where the mere act of installing a dependency or running a helper script doesn't compromise your whole system. We're almost there with our phones, we just need to rethink our desktops too. Of course I don't say you should use containers/sandboxes. It's a tradeoff everyone has to make, but there are many reasons some people (me included) prefer to sandbox everything as much as reasonably possible.

onesphere 3y ago

Shouldn't the OS already do containering with its processes (based on user)? That's kind of the [functional context] approach I take with: https://github.com/matrixApi/encapsule https://github.com/matrixApi/encapsule

miohtama 3y ago
Desktop and server operating system do not prevent any process to access file system. Any process can effectively steal any work you have on your file system, and also perform malware attacks by encrypting your files. This is not true for mobile operating systems like Android and iOS where processes cannot know about other processes or access file system.
insanitybit 3y ago
The typical User in linux is pretty unconstrained. They can view a lot of global resources, perform arbitrary system calls, view other processes, other users, etc. It's not really a tight sandbox. That's why Linux offers other, more powerful mechanisms for sandboxing such as namespaces, which are the backbone of containers.