Closed
Bug 248046
Opened 20 years ago
Closed 12 years ago
nsISignatureVerifier does not belong in CAPS
Categories
(Core :: Security: CAPS, defect)
Core
Security: CAPS
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: darin.moz, Assigned: dveditz)
References
Details
nsISignatureVerifier is used by Necko (for digest auth), mailnews, OJI, GFX
postscript layer, and xpinstall. It is implemented by PSM. However, CAPS
doesn't make use of it. IIRC it was put in CAPS for lack of a better place.
It should really be moved to some more generic location.
One choice would be to move it into Necko, but that seems odd. There are other
PSM interfaces that live in Necko for lack of a better place. Perhaps we should
come up with a better place for such interfaces.
Here's a few other security interfaces that exist (for some strange reason) as
part of Necko:
nsISecretDecoderRing.idl
nsISecureBrowserUI.idl
nsISecurityEventSink.idl
I propose moving all of these interfaces under security/manager/idl or
security/idl. Or, is there some good reason not to do that?
Reporter | ||
Comment 1•20 years ago
|
||
security/public or security/manager/public seem like good (better?) choices.
Comment 2•20 years ago
|
||
nsICryptoFIPSInfo.idl doesn't sound like it belongs into necko either...
note bug 53648 comment 0. although, security/manager != security/base...
some of those that require it are tier_9 or thereabouts, security is what, tier_40?
if you want the build to break, by all means, move them.
Comment 4•20 years ago
|
||
oh, something else... --disable-crypto should probably not cause the build to
fail. especially as it's the default.
Updated•15 years ago
|
QA Contact: caps
Comment 5•12 years ago
|
||
Moved to security/manager/ssl/public and probably being removed or replaced by bug 805305.
You need to log in
before you can comment on or make changes to this bug.
Description
•