Closed Bug 92054 Opened 23 years ago Closed 19 years ago

Expose MD5 to javascript

Categories

(Core Graveyard :: Security: UI, enhancement, P3)

1.0 Branch
enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: timeless, Assigned: darin.moz)

References

Details

(Keywords: helpwanted)

need idl, and need wrapping so javascript (or python or ...) can use the md5 
functions from nss.

The only question i can think of is should the md5 funcitons be limited to 
chrome users or could an html page be allowed access to them (probably not?)
marking future until we're lobbied for 2.1
Reporter, cc list are there specific bugs that would be blocking on this?
I've have to check on whether this is even possible.
Priority: -- → P3
Target Milestone: --- → Future
Why wouldn't this be possible? If MD5 is exposed in an XPCOM interface, then we
can make it callable from JS. And why should it be limited to chrome users? Why
not let web scripts call it too?
Mass assigning QA to ckritzer.
QA Contact: junruh → ckritzer
QA Contact: ckritzer → junruh
Really need this for a sidebar application.  

I'm surprised this hasn't been implemented.  Adding helpwanted
Keywords: helpwanted
Version: 2.1 → 2.4
Mass reassign ssaux bugs to nobody
Assignee: ssaux → nobody
nsISignatureVerifier (under mozilla/caps) exposes MD5 to JavaScript.  Is this
bug fixed?
Mass change "Future" target milestone to "--" on bugs that now are assigned to
nobody.  Those targets reflected the prioritization of past PSM management.
Many of these should be marked invalid or wontfix, I think.
Target Milestone: Future → ---
*cough* *cough*

none of the functions on that interface are scriptable, nor is that interface.

js> Components.interfaces.nsIPrincipal
js> Components.interfaces.nsISignatureVerifier
js> build()
built on Apr  8 2004 at 12:29:16

this is a trunk build, some modifications are pending/posted (e.g. xpcshell is 
using its own scriptsecuritymanager because soap sucks)
Assignee: nobody → darin
Product: PSM → Core
see also bug 292368
No longer blocks: link-fingerprints
It seems the work will happen on bug 292368; adding dependency to keep this
bug's dependency-list (rather than resolving this as a dupe).
Depends on: 292368
Fixed by dougt's patch for bug 292368
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Version: psm2.4 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.