with the amount of effort that goes into tooling on tooling on tooling wrapped in tooling we subject ourselves to, you would think we could come up with a secure-ish execution environment for all the random shit we run :\
Vendetta9076@sh.itjust.works
on 09 Nov 06:42
collapse
We had one. Its called VMs. Then the malware got smarter. Then the VMS got smarter. Then the malware got smarter. Then the VMS got smarter. Then the malware got smarter. Then the VMS got smarter. Then the malware got smarter.
VM’s aren’t great for development. The performance is poor and the DX is a pita so devs do dumb shit like mount their keys or entire home directory inside it negating the security benefits.
Thinking more along the lines of firejail seamlessly integrated with pip/venv/nvm/composer/whatever.
I think deno has greatly improved security sandboxing?
But yea you are 100% correct… It’s always going to be a never ending arms race. The status quo is just ridiculous.
Vendetta9076@sh.itjust.works
on 09 Nov 14:13
collapse
threaded - newest
with the amount of effort that goes into tooling on tooling on tooling wrapped in tooling we subject ourselves to, you would think we could come up with a secure-ish execution environment for all the random shit we run :\
We had one. Its called VMs. Then the malware got smarter. Then the VMS got smarter. Then the malware got smarter. Then the VMS got smarter. Then the malware got smarter. Then the VMS got smarter. Then the malware got smarter.
VM’s aren’t great for development. The performance is poor and the DX is a pita so devs do dumb shit like mount their keys or entire home directory inside it negating the security benefits.
Thinking more along the lines of firejail seamlessly integrated with pip/venv/nvm/composer/whatever.
I think deno has greatly improved security sandboxing?
But yea you are 100% correct… It’s always going to be a never ending arms race. The status quo is just ridiculous.
You’re entirely correct. The Status quo sucks ass