4 ms·
> VSCode can prevent installation of all but allowlisted extensions by policy. Companies using that are probably the reason for, or at least a big motivator fo
by TeMPOraL 3y ago
> VSCode can prevent installation of all but allowlisted extensions by policy.
Companies using that are probably the reason for, or at least a big motivator for, the feature in question. Lots of developer creativity is spent on working around corporate "security" practices that otherwise prevent work from being done.
- 1letterunixname 3y agoHow well would it work to allow every plugin to be used on confidential systems and protected without any sort of review? There's no way to denylist the way out of preventing a keylogger or malicious look-alike plugin retroactively. I think you're painting with a broad brush lacking nuance or understanding the concerns involved.
- TeMPOraL 3y agoI'm painting with a broad brush indeed, as all my nuance has been lost dealing with bullshit like being able to 5x my coding speed by (ab)using my "local admin" rights to discover which magic folders are on the Windows Defender exclusions list, hardcoded by corporate policy, and moving all my stuff there, while seeing requests to kindly just allow us to add our stuff to exclusions locally rejected with responses like "nope, and surely we can resolve the slowdown this causes by reimbursing you for a cooling pad for your laptop".
- 1letterunixname 3y agoWell, that's all well-and-good. You have to deal with the possible and the permitted rather than than complain about how you would do things your way. It's not your company and not your risk. Any time you break legitimate security rules you're putting your job and the jobs of everyone else at risk should there be a massive breach. No one in corporate uses WD because it's unmanaged. OTOH, MDE P1+VM is a steaming pile of shit that arbitrarily deletes things on untold millions of end-user devices because of the way Microsoft doesn't do properly risk management (canary) for new definitions.