wubi and umenu executables are not signed with a code signing certificate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Wubi |
Fix Released
|
Low
|
Evan | ||
Ubuntu |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When executing the wubi or umenu executables on Windows Vista with UAC enabled, the untrusted UAC prompt is displayed.
This occurs because these executables are not signed by a code signing certificate, or the certificate is not issued by an authority in the "Trusted Root Certification Authorities" local machine (NOT user) certificate store.
It may be worth considering using a code signing certificate from VeriSign or Thawte to perform timestamped Authenticode signing of these executables, this appears more professional to consumers using Vista.
I've attached a screenshot of what the two variants of the dialogs look like. The dialog on the right was obtained by signing a copy of wubi.exe with a self-signed certificate that I generated for testing purposes.
Changed in wubi: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in wubi: | |
assignee: | nobody → ago |
milestone: | none → 9.04 |
Changed in wubi: | |
status: | Fix Released → Fix Committed |
Changed in wubi: | |
status: | Fix Committed → Fix Released |
The signing was performed by running signtool.exe (command-line pre-supposes an installed version of the .NET Framework SDK):
"$(FrameworkSDK Dir)bin\ signtool. exe" sign /f X:\TestCodeSign ingCertificate. pfx /v wubi.exe