51440 - stan: Replace SSL_SecurityStatus()

Status: RESOLVED DUPLICATE of bug 78959

(NSS :: Libraries, enhancement, P3)

Description

[Nelson Bolyard (seldom reads bugmail)]

This was formerly bugsplat bug 351902

SSL_Security Status needs to be replaced with a well designed
API.  It should not return any compiled-in strings, because of 
the localization problems.  (Cert subject DNs are another matter).
It should clearly identify such things as :

- version of SSL (2, 3, TLS)
- cipher suite
- Whether the cipher suite is considered an "export" cipher or not.
- keybits and secret key bits (as it does now).

Comment 1

[John G. Myers]

As a caller to SSLSecurityStatus(), I only care about the effective strength of
the cipher and the identity of the other side.  I'm not sure why it returns both
keybits and secret key bits.

Comment 2

[Nelson Bolyard (seldom reads bugmail)]

As you know, SSL2's "40-bit" cipher suites actually used 128-bit
keys, of which 40 were encrypted and 88 were sent "in the clear".
Communicator's "Page Info" panel (for which this function was 
created) reports using words something like "using a 128 bit 
key of which 40 bits are secret".  

Comment 3

[Nelson Bolyard (seldom reads bugmail)]

Change target fix version for all "stan" RFEs to "Future".

Comment 4

[Wan-Teh Chang]

Is this a duplicate of bug #78959, SSL_GetChannelInfo()?

Comment 5

[Nelson Bolyard (seldom reads bugmail)]

Yes, these bugs are duplicates.  Although this bug is the older bug,
and the newer one really should be marked the duplicate, the newer
one has much more detail in it, so I'll mark this one as the duplicate.

*** This bug has been marked as a duplicate of 78959 ***