3 ms·
> potentially dozens of engineers and operators have access to that information For that you have to break Google's security. I (and other colleagues) actually
by euyyn 10y ago
> potentially dozens of engineers and operators have access to that information
For that you have to break Google's security. I (and other colleagues) actually felt safer about Google's stewardship of that information when we got to learn how it worked from inside, than before joining.
(I work for Google, but not on security, and don't speak for the company).
- angry-hacker 10y agoAnd why do you trust they implement it the way you saw? Is the code public? Even if it was, who guarantees they use the same implemention? I know many wonderful people working for the government wanting all the best for the people doesn't mean it always end up like that.
- euyyn 10y agoAll but the most IP-sensitive code at Google is visible to all Googlers, yes. And being able to tell what code is being executed by what machines in production is required for ops and reliability reasons in any big company anyway. But most important of all, it doesn't make sense to make what's arguably the best private security team write your defenses, to then not use them.