Closed Bug 369621 Opened 17 years ago Closed 11 years ago

refactor crypto key manager into an XPCOM service

Categories

(Toolkit :: Safe Browsing, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: tony, Assigned: tony)

Details

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
Closed: 11 years ago
Resolution: --- → WONTFIX
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.