News for hackers. Stuff that matters.
Re:Mxc: Microsoft Execution Containers version 1.0.0 by 3eb7988a1663 on Saturday October 10, 2026 @12:23PM (#50034412)
Can I use this as a generic app permissions boundary or do I have to somehow fake it as an "agent"? We are well past the point where I need to be able to lock down that my music player has no ability to read my SSH keys or whatever.

Naturally, this will be gated to corporate customers - the plebs do not get access to better security unless they pay for a top tier license.

Re:Mxc: Microsoft Execution Containers version 1.0.0 by tomrod on Saturday October 10, 2026 @01:43PM (#50035254)
FANTASTIC question here. I've been locking down agents by running them as untrusted users (mostly linux here) as even docker boundaries aren't really great. Firecracker is a step in the right direction (older tech, sure, but useful). I really want a local hashicorp-like vault that I can give agents specific access permissions and it can take forever to review and manage those access boundaries.
Re:Mxc: Microsoft Execution Containers version 1.0.0 by trollbridge on Sunday October 11, 2026 @04:07AM (#50040694)
Indeed, Linux users pretty much provide enough protection and if you are willing to fiddle with SELinux you can get whatever you need.
Re:Mxc: Microsoft Execution Containers version 1.0.0 by doctorpangloss on Saturday October 10, 2026 @02:57PM (#50035983)
I guess buy a Mac then.
Re:Mxc: Microsoft Execution Containers version 1.0.0 by tuwtuwtuwtuw on Saturday October 10, 2026 @01:36PM (#50035189)
There are many things that would be good to lock down. NPM install comes to mind.

I wonder if I will be able to integrate this with dev containers somehow, so my dev container could run in stricter isolation.

Re:Mxc: Microsoft Execution Containers version 1.0.0 by tomrod on Saturday October 10, 2026 @01:44PM (#50035266)
I've seen folks using the VS Code workspaces concept for this. It's a bit limited but a good step in the direction I prefer.
Re:Mxc: Microsoft Execution Containers version 1.0.0 by tuwtuwtuwtuw on Saturday October 10, 2026 @02:30PM (#50035716)
VS Code workspaces doesn't seem to offer any protection:

https://code.visualstudio.com/docs/editing/workspaces/worksp...

Maybe you use GitHub codespaces?

Re:Mxc: Microsoft Execution Containers version 1.0.0 by tomrod on Saturday October 10, 2026 @02:43PM (#50035835)
No, I did mean VS Code workspaces. Now I'm going to go down this rabbit hole to better understand the boundary limits :)
Re:Mxc: Microsoft Execution Containers version 1.0.0 by tuwtuwtuwtuw on Saturday October 10, 2026 @03:52PM (#50036514)
I did some reading of the docs and can't see anything in VS Code workspaces that would help.