When we release a new version of our setup executable, users downloading it on Google Chrome see the attached error.
After enough people run the executable, the error goes away. However, we need someone that can recommend a permanent solution (one that can be done ahead of time to prevent any users from seeing the warning) or can fix the warning for us each time we release a new version.
We host our setup files on Amazon S3 so Google will not "whitelist" our domain name.
Looking to make some money?
- Set your budget and the time frame
- Outline your proposal
- Get paid for your work
Bids on this Project
Orenburg, Russian Federation
Allen, United States
Developer proficient with PHP, CSS, HTML, Java, and many open source projects.