Chromium developer C++
Tasks:
- Review the code of the two previous developers, which the customer will provide during the collaboration. Discuss with the customer whether to use their code implementations or create your own. Once a decision has been made on whether to use the existing implementations or create your own, act accordingly.
- Discuss all future project tasks, not just those related to the current stage. Discuss in detail so that the contractor has a 100% clear understanding of the customer's project.
- Implement canvas spoofing functionality, install socks4/5 or http with authentication, spoof client rects, spoof webrtc, install doh (DNS over HTTPS). It is also necessary to use secure data exchange between Chromium and any process that runs Chromium. This has already been implemented by the previous developer, so we want the data transfer to be done in the same way.
- Test the code so that there are no errors when transferring it to the customer. The code must support compilation and execution for Linux, Windows, and macOS.
- Provide the source code in a private GitLab repository and brief instructions on how to compile the code for Windows. The customer will provide the repository to the contractor.
- The quality of the spoofing will be verified by the customer on checkers by running the Chromium modification. The task will be considered complete if all functions work properly.
NOTE! - More detailed tasks for the implementation of certain functionalities are described in the technical specifications that the customer pinned to the project like a file.
