Closed Bug 683700 Opened 13 years ago Closed 13 years ago

Static download page needed for the Firefox Integrity Check program

Categories

(support.mozilla.org :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
2011-09-13

People

(Reporter: verdi, Assigned: rrosario)

Details

Rob Strong and I are working on a system to gather information about broken Firefox installs. He's developed a Windows program that I'll direct users (in a 1:1 interaction) to download and run on their computer. I will create a SUMO article with instructions for downloading and running this program and it should link to a static page on support.mozilla.com that has the actual link to download the file.

This static page should contain the following text:
This program will check for problems with your Firefox installation and recommend actions you can take to fix them. No personal information will be sent to Mozilla by this program.

Privacy Policy [link to http://www.mozilla.org/en-US/legal/privacy/firefox.html]

Security Reminder:
* Mozilla will only provide diagnostic programs directly from an official mozilla.com website, such as support.mozilla.com.
* Mozilla will never send email messages with attached programs or files or ask you for any sensitive information such as passwords.
Target Milestone: --- → 2011-09-06
The 9-06 train already left the station, unless this is really urgent 9-13 is the next opportunity.
Target Milestone: 2011-09-06 → 2011-09-13
It's pretty urgent. I need time before the end of the quarter to get some results. An extra week would be helpful.
Assignee: nobody → rrosario
https://github.com/jsocol/kitsune/commit/70a08100db4b0184b7d56f5dbc1860b280a91015

Page at: /download-firefox-integrity-check
Program expected to be at: /media/downloads/FirefoxIntegrityCheck.exe
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Verified page displays as expected with correct button and file links, .exe file does not exist at this time [expected].
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.