The (lack of) security of VSCode has always been astounding. People have asked for sandboxing extensions for years [0] with little to no progress, and issues have been discussed a lot (e.g. [1][2]). I guess it hasn't been a big issue, likely because most developers are not complete idiots. But it only takes one developer and one bad extension to consequences like this. I mean, I understand that it is hard to sandbox…
GitHub confirms breach of 3,800 repos via malicious VSCode extension
111–120 of 488 posts
Re: GitHub confirms breach of 3,800 repos via malicious VSCode extension
#112I really hope this pushes Microsoft to add a explicit permission system to VS Code extensions, and improve security of dev containers.
Migrate off vscode already.
Re: GitHub confirms breach of 3,800 repos via malicious VSCode extension
#113Maybe I'm missing something really obvious, but... 3,800 repos? I guess I find it kind of surprising they have that many!
Re: GitHub confirms breach of 3,800 repos via malicious VSCode extension
#114Earlier quoted context omitted.
podman seems to handle rootless namespaces just fine, minor caveat for some perf overhead but it's not the end of the world.
And volumes. Volumes are not fun with podman. Ironically my team tried GitHub Codespaces and never looked back. Super cheap and uses DevContainers.
Re: GitHub confirms breach of 3,800 repos via malicious VSCode extension
#115Re: GitHub confirms breach of 3,800 repos via malicious VSCode extension
#116If only the company behind VSCode, the company behind NPM and the company behind GitHub could get together and figure out a solution to this.
Re: GitHub confirms breach of 3,800 repos via malicious VSCode extension
#117Earlier quoted context omitted.
In my personal experience, give it a decade or two, and any corporation will accumulate hundreds (or even thousands) of abandoned internal repos containing discontinued services, POCs/prototypes that never went anywhere, etc – people forget to archive them, or aren't sure whether something is still in use or not so err on the safe side. AI is making this even worse. With coding agents, anyone can throw together a qui…
Maybe though AI will make it better, assign agents to monitor, maintain and keep repos up to date or via A2A refer them to an agent to dispose of them in accordance with company requirements. I actually think AI will greatly help this type of problem.
Re: GitHub confirms breach of 3,800 repos via malicious VSCode extension
#118Re: GitHub confirms breach of 3,800 repos via malicious VSCode extension
#119Re: GitHub confirms breach of 3,800 repos via malicious VSCode extension
#120I really hope this pushes Microsoft to add a explicit permission system to VS Code extensions, and improve security of dev containers.
I really hope this pushes users (here: devs and maintainers) to decrease their reliance on Microsoft and especially stop outsourcing security to them. Migrate off vscode already.
Zed is the closest thing I've found to meet my needs, and I do plan to try it. However it's dev container support looks to be lacking in some important ways so we'll see.