Closed Bug 306474 Opened 20 years ago Closed 12 years ago

Plugin finder should support and use xpinstall crypto hashes

Categories

(Toolkit Graveyard :: Plugin Finder Service, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: dveditz, Unassigned)

References

Details

(Keywords: meta)

bug 302284 added support for crypto hashes to validate xpis downloaded from our mirror network. As part of that we added initManagerWithHashes() to nsIXPInstallManager as a replacement for initManagerFromChrome(). There would be three parts to this: Get hashes into the database Write hashes into the rdf files (presumably ignored by previous versions) Change pluginInstallService.js in the client to call the new API This is most important for any plugins hosted on our mirror network. If we point to a vendor's download site and trust it we can pass null for the hash to skip hash checking. If we point to the vendor and the vendor makes silent in-place security updates (e.g. we point to a "latest" directory) then we MUST NOT use hashing for those files.
The client part of this was fixed in bug 384925 (pfs "supports" it); the server part ("using" it) is in bug 385037
Depends on: 384925
Flags: blocking-firefox3?
Summary: Plugin finder should support xpinstall crypto hashes → Plugin finder should support and use xpinstall crypto hashes
Flags: blocking-firefox3? → blocking-firefox3+
Assignee: nobody → gavin.sharp
Target Milestone: --- → Firefox 3 M8
It looks to me like this was fixed in bug 384925. Is there anything left to do here?
Oh, I guess I missed comment 2. Is this a tracking bug, then?
Keywords: meta
Flags: blocking-firefox3+ → blocking-firefox3-
Assignee: gavin.sharp → nobody
Target Milestone: Firefox 3 M8 → ---
Product: Firefox → Toolkit
XPI plugins are long dead. Next up: non-XPI plugins. ;-)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.