2 ms·
This is an ad hominem dressed up as a comment about company policy: “if only you worked at a company that didn’t suck, like I did, you would have actual securit
by saagarjha 4y ago
This is an ad hominem dressed up as a comment about company policy: “if only you worked at a company that didn’t suck, like I did, you would have actual security and wouldn’t file stupid bugs like these!”
We both know that Google does better than most at endpoint security. In some cases it’s possible to argue that they are the best. What we definitely don’t need is you to be superior about it: it’s part of the reason why (ex-)Googlers have a poor reputation.
In this case, having technical measures that avoid sensitive things ending up on developer machines is an excellent way to help improve your security posture. That said, it definitely doesn’t mean you shouldn’t be unconcerned about code execution on developer machines. There’s a reason that internal red team exercises distinguish between external access and already having a foothold on a machine.
In this case isn’t obviously not a specific failure in Google’s security policy that package managers don’t do namespacing, but if I was on the team and I received this report I would at least think about whether there is something I would want to do here to improve the situation, similar to existing efforts to prevent attacks like paste bracketing or trivial keylogging.