2 ms·
I believe extensions inherit the permissions that the editor has already - so if you've given Cursor or VS Code permission to access a folder any extensions the
by simonw 1y ago
I believe extensions inherit the permissions that the editor has already - so if you've given Cursor or VS Code permission to access a folder any extensions they run later can access it too.
I agree, this seems bad! Sandboxing is still a very weakly implemented craft for most applications, especially those that run extensions or plugins.
(I build a lot of software that runs plugins and has no sandboxing at all, and it really frustrates me. I'm constantly looking out for cross-platform Python-friendly sandboxing tech that might help with this in the future.)
- TechDebtDevin 1y agoIts called a docker container ;)
- mistrial9 1y ago> Sandboxing is still a very weakly implemented craft for most applications voice of decades past -- sandboxing is very well known and deeply implemented in many aspects of ordinary daily computing; sandboxing is endlessly difficult and can be mis-applied; people who want to break into things and steal and wreak havoc ruin software environments for everyone else.
- octopoc 1y agoI’m monitoring this area as well. You’ve probably run across these already but extism, a polyglot plugin framework, can be hosted in Python[1] and has evolving support for writing plugins in Python [2]. Another option is container2wasm[3]. I actually tried running clickhouse in container2wasm and it crashed because it only had one CPU core, so YMMV—although that shouldn’t be a problem for Python (or any code custom built for your plugin framework). For me, I want to avoid separate processes. I definitely want to avoid separate VMs. [1] https://github.com/extism/python-sdk https://github.com/extism/python-sdk [2] https://github.com/extism/python-pdk https://github.com/extism/python-pdk [3] https://github.com/container2wasm/container2wasm https://github.com/container2wasm/container2wasm