Closed Bug 776060 Opened 12 years ago Closed 7 years ago

Provide Async API for validating JAR signatures

Categories

(Core :: Networking: JAR, defect, P5)

Product:
Core
Component:
Networking: JAR
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: briansmith, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-would-take])

+++ This bug was initially created as a clone of Bug #774949 +++ We need a new API for validating JAR signatures that is asynchronous and which can apply restrictions on which certificates are acceptable (in particular, which CAs is acceptable). Such an API may be useful for implementing bug 774949.
Blocks: 774949
This was done in bug 772365 (nsIX509CertDB.openSignedJARFile), however bug 772365 implemented a restricted version that requires the SHA1-Digest-Manifest entry in the signature file. For extensions, for compatibility reasons, we cannot have the same restriction, so we'll need to extend the implementation of openSignedJARFile to take an option to verify JARs without SHA1-Digest-Manifest.
Depends on: sign-packaged-apps
No longer depends on: 804663
Assignee: brian → nobody
Whiteboard: [necko-would-take]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
This isn't necessary any longer.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.