[File Download Access Prevention] Add helper obfuscation methods Initial simple functions for obfuscating and deobfuscating data using crypto::Aead which will be used to make the file contents inaccessible while the deep scan verdict is not received yet. The key is generated randomly and reused for all downloads throughout the chrome lifetime. This might change later on as we might add key rotation, storage and derivation features in the future, but this feature acts as a deterrent for enterprise users and does not need to be secure for our current use case. Will have follow-up CL for adding support for variable chunk sizes by prepending the current chunk's size as metadata to the encrypted chunk. For more info see design doc go/cbe-dpr-download-access-prevention-dd. Bug: b/349858060 Change-Id: I6b667457985fa788c575ff143d8808332ccc90d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5660244 Commit-Queue: Haihan Chen <haihan@google.com> Reviewed-by: Dominique Fauteux-Chapleau <domfc@chromium.org> Reviewed-by: Adam Langley <agl@chromium.org> Cr-Commit-Position: refs/heads/main@{#1335444}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.