3 ms·
> How do you develop locally while making sure the privacy/security of your system is not compromised? For me and all developers I've interacted with around me
by filleokus 4y ago
> How do you develop locally while making sure the privacy/security of your system is not compromised?
For me and all developers I've interacted with around me, I think the answer is "we don't [make sure that the privacy/security of our systems are not compromised]".
I would bet it's fairly common to have multiple machines however. My work machine has never seen my banking credentials or HN password. But of course a bunch of work-related sensitive stuff. And I of course have a bunch of programming stuff on my home machine, which I mostly just hope are not doing nefarious stuff.
If I wanted to up my security (in just this aspect) I would probably go for a simple VM as a first step. Resonable enough separation, while not causing too much havoc in my workflow. No folder sharing, just SSH in to it and treat it like a remote VPS, but local.
The next step up, which also increases isolation between other stuff (should I really trust any application to not do bad stuff?) would probably be QubeOS[1]. While I haven't used it, I would guess it would be a pretty major change to my current setup.
[1]: https://www.qubes-os.org/intro/ https://www.qubes-os.org/intro/
- cjbprime 4y agoAgree with all of this, except I'd add Docker containers as a less severe step before going all the way to something like Qubes. Since the OP mentions Python and Node libraries, it's likely they're compatible with being run inside Docker containers, which should do a passable-but-not-perfect job at isolation.