Add a functionality to Chromium source code
Budget: $30 – $250 USD
You need to add a functionality to Chromium source code, every flags (process arguments) being passed have to be encrypted (using AES-256, the key/iv can be built-in the source code itself, it's alright), meaning, if we run Chromium and we do ps -ex, you should have no way of understanding the flags (by flag I mean process args) being passed (ALL OF THEM), Example:
- /usr/lib/chromium/chromium --type=renderer --field-trial-handle=9828438894882116858,5246595339552873915,131072 --lang=en-GB --disable-client-side-phishing-detection...
This would becomes:
- /usr/lib/chromium/chromium XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (encrypted AES string)
It has to work on Linux/Mac/Windows, you have to make sure that every processes/sub-processes spawned by Chromium itself (as they spawn quite many processes for tabs, zygote...) are covered, there should be absolutely no way to tell which flags are being passed. If ever it matters, it has to work both in headful and headless.
We will start Chromium as well by using directly encrypted flags, you have to prove that it works by doing a simple NodeJS program where you do a spawn/exec with encrypted flags.
You are responsible of sending Chromium sources (just the files that you've modified) as well as a Linux or Windows BINARY that we will execute in a VM to proves that it works.
You must work on Chromium v93.
- /usr/lib/chromium/chromium --type=renderer --field-trial-handle=9828438894882116858,5246595339552873915,131072 --lang=en-GB --disable-client-side-phishing-detection...
This would becomes:
- /usr/lib/chromium/chromium XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (encrypted AES string)
It has to work on Linux/Mac/Windows, you have to make sure that every processes/sub-processes spawned by Chromium itself (as they spawn quite many processes for tabs, zygote...) are covered, there should be absolutely no way to tell which flags are being passed. If ever it matters, it has to work both in headful and headless.
We will start Chromium as well by using directly encrypted flags, you have to prove that it works by doing a simple NodeJS program where you do a spawn/exec with encrypted flags.
You are responsible of sending Chromium sources (just the files that you've modified) as well as a Linux or Windows BINARY that we will execute in a VM to proves that it works.
You must work on Chromium v93.