Publisher guidance for uncommon-download warning on signed private installer
I publish NinePane Connector at https://ninepane.com. On September 12, 2026, a Firefox test on Windows displayed NinePane-Connector-Setup-0.8.56-Windows-x64.exe as not co… (czytaj dalej)
I publish NinePane Connector at https://ninepane.com. On September 12, 2026, a Firefox test on Windows displayed NinePane-Connector-Setup-0.8.56-Windows-x64.exe as not commonly downloaded, with Remove file and Allow download controls. I have two matching Firefox screenshots of the warning.
The intended release candidate is distributed through our private authenticated test route. These screenshots do not establish the exact final download URL or completed bytes. The exact Firefox version and capture-time Windows build were not recorded, so I have not guessed them in this form.
The intended local candidate was independently checked as validly Authenticode signed by NINEPANE STUDIO with a timestamp. That identifies the signed local file; it is not proof of safety or of the blocked browser copy's exact bytes. We are not asserting malware detection or requesting a way to bypass the warning.
Which official publisher-support or assessment route applies to Firefox's uncommon-executable warning? Is there a supported way to obtain classification or remediation guidance without publishing a private installer or sharing login credentials? We have already reported the related Chrome warning to Google; should a publisher take any separate Firefox-specific action?
No installer, credentials, session data or unrelated browser diagnostics are included.