Chromium developer C++
The technical specifications are described in the attached document. Task details in the attached document.
Tasks:
- task 12 - implement AudioContext replacement functionality and fingerprint specification in the command line when launching Chromium
task 32 - implement synchronizer functionality (currently only for Windows)
task 4 - implement the functionality of setting and receiving passwords
task 6 - implement the functionality of setting webRTC via the command line when launching Chromium
task 20 - implement the functionality of setting DNT via the command line when launching Chromium
This is included in the cost of the current stage.
Remark: at the moment, data transfer to chromium will be carried out via the command line instead of the specified encrypted pipe between the process and Chromium; this has been moved to the end of all tasks.
- Test the code so that there are no errors when delivering to the client. The code must support compilation and execution for Linux, Windows, and macOS. This is included in the cost of the current stage.
- Provide the source code in a private GitLab repository and a brief instruction on compiling the code for Windows, Linux, macOS. The client will provide the repository to the executor. This is included in the cost of the current stage.
- The quality of the spoofing will be checked by the client on checkers by launching the Chromium modification. The task will be considered completed if all functions work properly.
REMARK! - More detailed tasks for implementing specific functional capabilities are described in the technical specification, which the client pint to this project. After the price has been discussed and set on the site, it is no longer discussed with the contractor and is fixed and does not depend on the time of completion by the contractor.
