Comment by danlitt 3 days ago Same reason people give postgres, php, or any other program a user account. 3 comments danlitt Reply dcow 3 days ago Why should it be? We have containers and capabilities… thwarted 3 days ago Containers are often used with user namespaces, which is literally another (set of) user account(s). khalic 3 days ago Yes but the encompassing service has the account, not the agent. You can completely segregate it from the rest of the system, like you’d treat an intruder
dcow 3 days ago Why should it be? We have containers and capabilities… thwarted 3 days ago Containers are often used with user namespaces, which is literally another (set of) user account(s). khalic 3 days ago Yes but the encompassing service has the account, not the agent. You can completely segregate it from the rest of the system, like you’d treat an intruder
thwarted 3 days ago Containers are often used with user namespaces, which is literally another (set of) user account(s). khalic 3 days ago Yes but the encompassing service has the account, not the agent. You can completely segregate it from the rest of the system, like you’d treat an intruder
khalic 3 days ago Yes but the encompassing service has the account, not the agent. You can completely segregate it from the rest of the system, like you’d treat an intruder
Why should it be? We have containers and capabilities…
Containers are often used with user namespaces, which is literally another (set of) user account(s).
Yes but the encompassing service has the account, not the agent. You can completely segregate it from the rest of the system, like you’d treat an intruder