Closed Bug 87881 Opened 24 years ago Closed 17 years ago

Key db password timeout enhancements.

Categories

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

Product:
Core Graveyard
Component:
Security: UI
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: ssaux, Unassigned)

Details

We may want to have the master db timeout have a slightly different semantic: Rather than X minutes of no-private-key operations, we could tie is to X minutes since the passwd was last requested. This is more restrictive than the current behavior which is X minutes of non-private key activity. Potentially could be a different option.
-> future P4
Priority: -- → P4
Target Milestone: --- → Future
Keywords: nsenterprise
removing nsenterprise keyword from PSM bugs with target milestone of future.
Keywords: nsenterprise
Mass assigning QA to ckritzer.
QA Contact: junruh → ckritzer
QA Contact: ckritzer → junruh
Mass reassign ssaux bugs to nobody
Assignee: ssaux → nobody
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 → ---
Product: PSM → Core
QA Contact: junruh → ui
Version: psm2.0 → 1.0 Branch
there doesn't seem to be much demand for this. i'm going to wontfix, if someone objects, they can post a patch :).
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Version: 1.0 Branch → Trunk
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.