Closed Bug 728182 Opened 12 years ago Closed 12 years ago

maybe purchase mac code signing key

Categories

(Release Engineering :: General, defect, P4)

Product:
Release Engineering
Component:
General
Platform:
x86_64
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 752613

People

(Reporter: bhearsum, Unassigned)

References

Details

(Whiteboard: [signing][10.8]) 

Based on what I've read of the OS X 10.8 app requirements () and this page about signing: https://developer.apple.com/library/mac/#documentation/ToolsLanguages/Conceptual/OSXWorkflowGuide/CodeSigning/CodeSigning.html, it seems to me that we need to have an Apple-signed certificate in order to properly sign Firefox. We should verify if this is the case or not, and if so, purchase one.
I think we can defer this until we start looking at bug 727895. We can use our existing authenticode certificate in the meantime.
Assignee: bhearsum → nobody
Priority: -- → P3
No longer blocks: 400296
Component: Release Engineering → Release Engineering: Automation
OS: All → Mac OS X
Priority: P3 → --
QA Contact: release → catlee
Hardware: All → x86_64
Whiteboard: [signing][10.8]
Priority: -- → P4
We ended up getting Developer IDs. This was all tracked in bug 752613.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.