Closed Bug 114751 Opened 23 years ago Closed 23 years ago

Fix PSM use of nsDialogParamsBlock.cpp was: Cert Enrollment is broken when using a hardware device.

Categories

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

1.0 Branch
x86
Windows 2000
defect

Tracking

(Not tracked)

VERIFIED FIXED
psm2.2

People

(Reporter: ssaux, Assigned: ssaux)

References

()

Details

Attachments

(1 file)

Using the internal Reg Authority to access certificates.netscape.com Using an ActivCard hardware device. Behavior is enter ldap name/pwd. Get prompted with the key escrow dialog. click on OK The device chooser never appears. The keys are not generated. The request is not sent to the server. Expected: The device chooser lets you select the device you want, the keys are generated, the request is sent.
Priority: -- → P1
Target Milestone: --- → 2.2
Whereever PSM needs to set a potentially large number of parameters for a dialog, SetNumberStrings is called. The indexes are now started at zero. PSM now correctly treats Int and String indexes are separate. I.e., SetInt(0,1); SetString(0,somestring); is ok. The following functionality was affected: cert picker. client auth cert chooser, token chooser, delete cert (all changes in the xul/js).
kai, can you review.
Keywords: patch, review
Summary: Cert Enrollment is broken when using a hardware device. → Fix PSM use of nsDialogParamsBlock.cpp was: Cert Enrollment is broken when using a hardware device.
Comment on attachment 62134 [details] [diff] [review] Patch make all of PSM code agree with nsDialogParams.cpp implementation r=kaie
Attachment #62134 - Flags: review+
Comment on attachment 62134 [details] [diff] [review] Patch make all of PSM code agree with nsDialogParams.cpp implementation sr=mscott
Attachment #62134 - Flags: superreview+
checked in => fixed
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
*** Bug 115304 has been marked as a duplicate of this bug. ***
Verified.
Status: RESOLVED → VERIFIED
I don't want to reopen this bug, but I found something related. PSM uses a subclass of nsDialogParamBlock, named nsPKIParamBlock. The implementation of that class adds the ability to pass an array of pointers. It has hardcoded to subtract -1 from the given index. In order to be consistent, it might make sense to adjust the security code, in order to be consistent with nsDialogParamBlock. On the other hand, this classes uses a dynamic array, and passing a zero index might not work, anyway.
I think I looked at this and I don't think I saw "wrong code". Fixing it just to be consistent is too much work and risk.
Product: PSM → Core
Version: psm2.2 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: