Re:Introducing Abseil, a new common libraries project
by joshuamorton on Thursday September 28, 2017 @01:50AM
(#15354951)
>Since Google's source code is one of the company's most important assets, security features are a key consideration in Piper's design. Piper supports file-level access control lists. Most of the repository is visible to all Piper users;d however, important configuration files or files including business-critical algorithms can be more tightly controlled. In addition, read and write access to files in Piper is logged. If sensitive data is accidentally committed to Piper, the file in question can be purged. The read logs allow administrators to determine if anyone accessed the problematic file before it was removed.
From [1]. Essentially, there are files and changes that I cannot view the source of.
Re:Introducing Abseil, a new common libraries project
by kerneis on Thursday September 28, 2017 @05:33AM
(#15355869)
But where the real magic happens is that you can still build them, even if you cannot read them, if they are required as (direct or indirect) dependencies of your code.
From [1]. Essentially, there are files and changes that I cannot view the source of.
[1]: https://cacm.acm.org/magazines/2016/7/204032-why-google-stor...