Closed Bug 643816 Opened 9 years ago Closed 9 years ago

D3DCompiler_42.dll and d3dx9_42.dll signed by Mozilla, not Microsoft

Categories

(Release Engineering :: General, defect)

x86
Windows 7
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rain1, Assigned: catlee)

References

Details

Attachments

(1 file, 1 obsolete file)

Firefox 4.0 on Windows: I noticed that the copies of these two DLLs in the Firefox folder are signed by Mozilla, not Microsoft. The system versions (in C:\Windows\System32) are signed by Microsoft, so it seems as if our release process is overwriting those signatures.

I think these DLLs should either be co-signed by Mozilla if possible, or else just left alone as signed by Microsoft.
Yeah, probably better off not signing them at all.
Assignee: nobody → catlee
Attachment #521012 - Attachment is obsolete: true
Attachment #521906 - Flags: review?(bhearsum)
Attachment #521906 - Flags: review?(bhearsum) → review+
Comment on attachment 521906 [details] [diff] [review]
don't sign D3DCompiler_42.dll or d3dx9_42.dll

http://hg.mozilla.org/build/tools/rev/28dcc684794d
Attachment #521906 - Flags: checked-in+
Future releases shouldn't have this problem.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
(In reply to comment #6)
> Is the '42' ever going to change?

Sure it is. This number is the revision of the DirectX SDK install on the build host. '42' means August 2009 / February 2010. For example, if you use the June 2010 SDK, you get '43'.

So this number is going to change whenever our build slaves get a DirectX SDK update (not saying that this is needed at the moment).
Depends on: 673884
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.