refactor crypto key manager into an XPCOM service

RESOLVED WONTFIX

Status

()

RESOLVED WONTFIX
12 years ago
5 years ago

People

(Reporter: tony, Assigned: tony)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

12 years ago
The anti-phishing code has a key manager than holds onto the keys provided from the server via a getkey request.  Currently, it's a bit weird in that it initializes an instance of the key manager and attaches it to the .prototype of PROT_UrlCrypto:
http://lxr.mozilla.org/seamonkey/source/toolkit/components/url-classifier/content/url-crypto.js#68

Since the key manager just needs to be a singleton, it would make more sense for it to be an xpcom service.
I don't think this is relevant to the current code.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
Component: Phishing Protection → Phishing Protection
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.