Closed Bug 13794 Opened 25 years ago Closed 23 years ago

[ssl] - crypto js object

Categories

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

1.0 Branch
defect

Tracking

(Not tracked)

VERIFIED FIXED
psm2.0

People

(Reporter: dougt, Assigned: javi)

References

()

Details

(Keywords: helpwanted)

Need to implement cryto Javascript object and reflect it in the dom. This
object is present in 4.7.
Group: netscapeconfidential?
Depends on: 13785
No longer depends on: 13785
Blocks: 13785
changing QA contact from tever to junruh per paw
mass accepting ssl bugs.
Bulk move of all Networking-Core (to be deleted component) bugs to new
Networking component.
adding beta1 keyword and setting m14 checkpoint.
Keywords: beta1
PDT needs more data -- what do we lose by not doing this?
being able to tell if cartman is installed from a webpage.

crypto.version
Putting on PDT- radar for beta1.  No critical user, and we will smart upate on 
mass.
Whiteboard: [PDT-]
Need to following api's which are in nova:

    {"random",                 crypto_random,               0},
    {"generateCRMFRequest",    cmjs_generateCRMFRequest,    0},
    {"importUserCertificates", cmjs_importUserCertificates, 0},
    {"popChallengeResponse",   cmjs_popChallengeResponse,   0},
    {"signText",               cmjs_signText,               0},
    {"signTextEx",             cmjs_signTextEx,             0},
    {"alert",                  cmjs_alert,                  0},
    {"logout",                 cmjs_logout,                 0},
    {0}
*** Bug 28017 has been marked as a duplicate of this bug. ***
per conversation with mwelch.  Take a look at :

http://lxr.mozilla.org/seamonkey/source/xpinstall/src/nsSoftwareUpdate.cpp#437

for an example of how to get your js object into the dom.  if you have any 
questions about how to do this, give me a call.
Assignee: dougt → javi
Status: ASSIGNED → NEW
Accepting the bug.  Adding mwelch and lord to cc list.
Status: NEW → ASSIGNED
Blocks: 24886
Group: netscapeconfidential?
Javi thinks he can be done in the M17 timeframe, marking as such.
Keywords: beta1
Whiteboard: [PDT-]
Target Milestone: M14 → M17
Steps to Verify when fixed: 
1) Start Seamonkey, and visit http://warp/hardcore/cartman/cmcheck.html
Expected Results: The page should say "Cartman Detection Page" plus "Cartman 
is loaded"".

per phil --> nsbeta2
Keywords: nsbeta2
Putting on [nsbeta2+] radar.  
Whiteboard: [nsbeta2+]
I've got all the dom changes for this bug ready.  

I need someone to review them before I can check in.

dougt and/or jst, let me know how I can get the diffs to you.  There are quite a
few new files which will make it impractical to include the diffs as part of the
bug report.
javi -  send them via email.  I will review and test them out.
Any progress on this yet?
Component: Networking → Security: Crypto
The crypto object isn't completely ported, but enough of it has been ported to 
allow for key generation and PSM UI to work.

The only functionality that has not been ported is the signText method.  This is 
the JavaScript method that is used by some companies to autmoate the signing of 
sensitive data through a web interface.
Whiteboard: [nsbeta2+]
javi, you removed the [nsbeta2+] from Status Whiteboard, but left nsbeta2 in 
keyword filed.  Is this because enough works for now, and no more work needed 
for beta2?  Did you have more to checkin for this?
Adding [NEED INFO]
Whiteboard: [NEED INFO]
The crypto object is as functional as we need it for PR2.  The only major
functionalit missing is form signing.  It's not on a PRD somewhere, so I'm not
sure if there are plans to put this in or not.  Removed nsbeta2 from status so
that PDT could determine whether to bump this to beta 3 or not.  There is no way
sign text would get done by PR2, not enough cycles. 

But this bug is not ready to be closed.
Putting on [nsbeta2-] radar. Not critical to beta2. 
Whiteboard: [NEED INFO] → [nsbeta2-]
Keywords: nsbeta2nsbeta3
Target Milestone: M17 → M18
Adding nsbeta2 keyword to bugs with nsbeta2 triage value in status field so the 
queries don't get screwed up
Keywords: nsbeta2
Blocks: 48444
marking nsbeta3-.  This is for a non-essential feature.
Whiteboard: [nsbeta2-] → [nsbeta2-][nsbeta3-]
*** Bug 55805 has been marked as a duplicate of this bug. ***
nsbeta1
Keywords: nsbeta1
Milestone 0.8 has been released. We should either resolve this bug or update its
milestone.
Setting milestone to future.
Target Milestone: M18 → Future
PSM 2.0
Component: Security: Crypto → Client Library
Product: Browser → PSM
Target Milestone: Future → 2.0
Version: other → 2.0
Keywords: nsbeta2, nsbeta3helpwanted
Whiteboard: [nsbeta2-][nsbeta3-]
crypto object is now present in PSM 2
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm2.0 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.