Closed Bug 113524 Opened 23 years ago Closed 20 years ago

Implement correct algorithm when downloading CA cert chains

Categories

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

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID
Milestone:
psm2.4

People

(Reporter: ssaux, Unassigned)

Details

Algorithm is as follows: If the chain chains to an already trusted root, the user [optionally?] gets a success dialog, but is not asked to trust anything. If the chain chains to a root that is not already trusted, the user is prompted as to whether they want to trust the existing root. If the chain doesn't chain to any root, the user is prompted as to whether he wants to trust the ca highest in the chain (i.e,. closest to an hypothetical root).
depends on NSS 3.4
Priority: -- → P2
Target Milestone: --- → 2.2
nsbeta1
Keywords: nsbeta1
Keywords: nsbeta1 → nsbeta1-
Stephane, you seem only to describe what the current behaviour is. What new behaviour are you suggesting?
Keywords: nsbeta1
Keywords: nsbeta1-
Keywords: nsbeta1
Keywords: nsbeta1
OS: Windows 2000 → All
Hardware: PC → All
Target Milestone: 2.2 → 2.4
Version: 2.1 → 2.4
Mass reassign ssaux bugs to nobody
Assignee: ssaux → nobody
Product: PSM → Core
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
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.