550514 - calbscmp.dll missing digital signature

Status: RESOLVED INVALID

(Calendar :: Build Config, defect)

Description

[Tamara]

User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB0.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Build Identifier: Mozilla Thunderbird 3.03

Four digital signatures missing

Thunderbird:
SignTool Error: No signature found.
SignTool Error: File not valid: freebl3.dll

SignTool Error: No signature found.
SignTool Error: File not valid: nssdbm3.dll

SignTool Error: No signature found.
SignTool Error: File not valid: softokn3.dll

Mozilla Lightning:
SignTool Error: No signature found.
SignTool Error: File not valid: calbscmp.dll




Reproducible: Always

Steps to Reproduce:
N/A
Actual Results:  
Missing digital signatures

Expected Results:  
All files should be digitally signed.

Comment 1

[zug_treno]

(Partial) duplicate of mozilla.org bug 489961?

Comment 2

[Nathan Tuggy (:tuggyne)]

Yes. However, I wasn't able to find a dup for the Lightning component; I'll switch this bug to that only. (It would be nice if someone could verify that part.)

What tool are you using to verify signatures, and what setup?

Comment 3

[Tamara]

Hi - we are using Signtool.exe (version 6.0.6000.16384) from the Windows Vista SDK tools on Win 7 32-bit, using the following command line: signtool verify /pa /v {filename}

This is with beta 1 of Lightning, but I also verified it in the latest build (2010-03-07-09-comm-1.9.2).

Comment 4

[Stefan Sitter [:ssitter]]

See Bug 378730.

Comment 5

[Nathan Tuggy (:tuggyne)]

Got it. signtool wasn't giving me useful results for anything I tried it on, as I was using the wrong policy.

(In reply to comment #4)
I'll set this as a dependency for now; this bug is about signing a DLL from within the XPI, as opposed to signing the XPI proper.

Comment 6

[Philipp Kewisch [:Fallen][☁️📆]]

Norton Internet Security 2012 may delete our dll, marking it as "WS.Reputation.1", which basically means it is too new to be in the database, but may be a threat.

I have been told this is because our dll doesn't have a signature. In the long run the dll is going to go away, but if this is low effort maybe its worth a shot.

Comment 7

[Philipp Kewisch [:Fallen][☁️📆]]

dll has gone away, closing bug