Chromium C++ developer

The technical specifications and tasks details are described in the attached document, which the client pint to this project.

 
Tasks:

task 28 - Implement functionality for running Chromium through an authenticated proxy
task 10 - Implement functionality for overriding client rects and specifying the fingerprint in the proto config file when launching Chromium
task 5 - Implement the functionality to override UserAgent and UserAgentMetadata and specify settings in the proto config when launching Chromium
task 7 - Implement the functionality to override WebGL and specify the fingerprint in the proto config when launching Chromium
task 8 - Implement functionality to override WebGL info and specify WebGL metadata settings in the proto config when launching Chromium
task 9 - Implement functionality to override WebGPU in the proto config when launching Chromium
task 3 - Implement the functionality for setting start pages via the proto config when launching Chromium
task 37 - Remove pop-up windows in Chromium
task 13 - Implement the functionality for setting the screen resolution via the proto config when launching Chromium
task 14 (MediaDevices) - Implement functionality to set device media devices via the proto config when launching Chromium
task 14 (Timezone) - Implement functionality to set static and dynamic time zones via the proto config when launching Chromium
task 15 - Implement functionality to set system languages via a proto config file when Chromium starts
task 16 - Implement functionality to set dynamic geolocation when Chromium starts
task 17 - Implement functionality to override cpuCores via a proto config file when Chromium starts
task 18 - Implement functionality to override RAM via a proto config file when Chromium starts
task 19 - Implement functionality to block ports via a proto config file when Chromium starts
task 21 (DNS) - Implement the ability to specify DNS via a Proto configuration file when launching Chromium
task 21 (Save History) - Implement the ability to specify whether to save browser history via a Proto configuration file when launching Chromium

This is included in the cost of the current stage:

1. The code must be based on the latest release commit of the Chromium source code.

2. 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.

3. 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.

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.
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.