3 ms·
Or, learn your local OS' permission system, have it in a directory right next to your banking credentials (or something even more outrageous) and nothing could
by embedding-shape 5mo ago
Or, learn your local OS' permission system, have it in a directory right next to your banking credentials (or something even more outrageous) and nothing could go wrong even if you tried to.
- AnotherGoodName 5mo agoThis very thread was an example where it unintentionally got root access though.
- embedding-shape 5mo agoBecause of how Docker works, not because of how Unix permissions work.
- f33d5173 5mo agoUnix has always had incredibly weak protections between users. You shouldn't rely on it as a security boundary. Think of it as a "keep honest users honest" protection. And llms are not honest.
- ElectricalUnion 5mo agoThe protections between users are reasonably strong. Android uses them with great success, by isolating every vendor within their own user. Things start going to hell when everything runs under root for "practicality reasons", like the default, not-rootless Docker setup.
- amarant 5mo agoI've seen this sentiment a few times on HN recently I wonder where it comes from? The only thing I can think of is that if the protected files are on a unencrypted drive, then you could boot from a live-usb(or similar) where you have root and read anything. But that's completely irrelevant as we're talking about a piece of software running on a system without root. In this scenario Unix user permissions are safe, barring user error (such as accidentally granting root, like in this instance) Of course security holes happens, such as copy-fail, but it's pretty rare in the grand scheme of things, and tend to get patched quickly(like copy-fail was)
- CGamesPlay 5mo agoThat's a terrible distinction to make on a topic about how the coding agent gained root inadvertently.