3 ms·
The only way to know is to forge a malicious script that encrypts the filesystem, slip it into a popular library, and see who complains. Otherwise people will a
by laurent92 6y ago
The only way to know is to forge a malicious script that encrypts the filesystem, slip it into a popular library, and see who complains. Otherwise people will always take half-decisions, only masking the types of attacks they know about. This, or black hats are already using this backdoor silently.
Which makes me wonder: Should dev machines be considered high-risk? They run all sorts of software, with permissions loosened, then pass programs to CI tools, which build them and deploy to prod with AWS authentication tokens enabled... I’m shaking just seeing how many Chrome extensions my devs have (with all permissions enabled of course) when they access prod instances...
Should startup management (Safe environnements with Excel, no Chrome extensions, accessing the company’s bank accounts, etc) be done on separate machines than development activities?
- efortis 6y agoAbout the dev machines, yes, many places do consider them (and they are) high risk. I'd add to your list, the source code, future plans, etc. I do some basic steps to harden my dev machines: - A Chrome profile without extensions for developing for the most part. - The localhost is not 127.0.0.1 but a random IP under 127/8, with a random port. See https://news.ycombinator.com/item?id=20028108 https://news.ycombinator.com/item?id=20028108 - When creating SSH keys, add extra rounds (e.g. `ssh-keygen -a 64`) to make it harder to brute-force the passphrase.