4 ms·
I mean, of course it does. Most people run their development environments as their own user, and most package management systems have post-install script suppor
by annabellish 8y ago
I mean, of course it does. Most people run their development environments as their own user, and most package management systems have post-install script support.
Installing random software from the internet is problematic.
- vemv 8y agoI'd be interested in running my dev environment with a dedicated user account -with no access to the main account's personal files, credentials, etc-, do you know of any guides for doing so? (I could just give it a shot, but I reckon there will be gotchas)
- andreareina 8y agoWhat I do is use a VM as my development environment, managed by Vagrant. Any dependencies stay on the VM image.
- angry_octet 8y agoWhat platform? GUI or shell? Docker/LXD or a dev VM lets you access both simultaneously. Or create a separate user, but not as secure or convenient.
- vemv 8y agomacOS. Not much interested in VMs, for efficiency. Yeah I was playing with a separate user account, could get some basics working but I wonder how far could I get with that. What are the bigger security risks for that approach? Assuming constrained file permissions, and that no secrets are in ENV (https://gist.github.com/telent/9742059 https://gist.github.com/telent/9742059 )
- angry_octet 8y agoA normal user has full access to the kernel API. Always kernel info leaks, occasional easy exploits. On macos you can use Apple's native sandboxing. See for example http://mybyways.com/blog/creating-a-macos-sandbox-to-run-kodi http://mybyways.com/blog/creating-a-macos-sandbox-to-run-kod...