Setup Windows signing infrasctucture

RESOLVED FIXED in Thunderbird 3.0b4

Status

RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: gozer, Assigned: gozer)

Tracking

other
Thunderbird 3.0b4
Dependency tree / graph
Bug Flags:
blocking-thunderbird3 +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [no l10n impact][waiting for real cert])

(Assignee)

Description

10 years ago
We need a code signing certificate, make sure it's on one of these : <http://www.raaktechnologies.com/store/smart_cards.html>, and verify we can use the existing signing automation.
(Assignee)

Updated

10 years ago
Depends on: 499711
(Assignee)

Comment 1

10 years ago
Looks like there is a place beside verisign/thwate where one can buy authenticode certificates:

<http://www.tech-pro.net/code-signing-certificate.html>
(Assignee)

Comment 2

10 years ago
Progress update. I now have a Windows Signing VM that is able to successfully Authenticode Sign against signing certificates stored in the smartcard.

Need to get the signing automation working now.
(Assignee)

Updated

10 years ago
Depends on: 507442
(Assignee)

Comment 3

10 years ago
david, it's time to go ahead and purchase an actual code signing certificate.

Comodo: 180/year
Thwate: 299/year
Verisign: $499/year

I've heard various negative comments about comodo, and verisign is somewhat of big beast (and expensive), so I'd rather suggest we try Thwate for 1 year and see how that goes. Changing/replacing the certificate is simple, so not a big commitment.
a=davida
Assignee: nobody → gozer
Flags: blocking-thunderbird3+
Target Milestone: --- → Thunderbird 3.0b4
Whiteboard: [no l10n impact]
(Assignee)

Comment 5

10 years ago
Code signing certificate ordered, David, expect somebody from Thawte to contact you to verify company info.
Whiteboard: [no l10n impact] → [no l10n impact][waiting for real cert]
(Assignee)

Comment 6

10 years ago
Cert recieved! Tested signing automation with it, and all looks good.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.