Open Bug 47940 Opened 24 years ago Updated 2 years ago

dbck recovery mode

Categories

(NSS :: Tools, defect, P3)

Product:
NSS
Component:
Tools
Type:
defect

Tracking

(Not tracked)

People

(Reporter: bugz, Unassigned)

References

Details

needs callback implemented to correctly choose certs to keep.
moving to 3.2. Not much left to do.
Target Milestone: --- → 3.2
QA Contact: wtc → sonmi
Priority: P3 → P1
moving to 3.3 pending cert library changes that will be made later.
Target Milestone: 3.2 → 3.3
Target Milestone: 3.3 → 3.4
Ian, this bug is targeted at NSS 3.4, with priority P1. Please make sure you can get this fixed in 3.4. Does this also require making dbck a supported tool?
The whole problem with dbck is that it has fallen more and more out of step with the cert library as time goes by. Now, with the cert db code moved into softoken, it would be a considerably larger effort to attempt to get dbck working again. At this point, it would be almost as easy to implement it from scratch in perl (which if I had known perl at all at the time, I would have done to begin with). OTOH, the reason we haven't heard many cert db corruption complaints lately is that mozilla hasn't supported S/MIME. That alone accounts for 90% of corruption bugs. With that support upcoming, dbck may be more neccessary. Actually, what is most needed is an API function that "self-heals" the database, one that PSM could call. Most users will not want to deal with a command line tool. At any rate, I would predict it would take at least a week for me to get this going. That has to be considered in its priority viz. other bugs.
dbck will have to link directly with softoken code and include private header files from softoken. Two other low level cmd's do this already: blapitest and rsaperf. Someday we should probably organize the commands and separate out those commands which are tied to low level functions from those that are generic (or meant to be generic). bob
Deferred to 4.0 and lowered priority to P2.
Priority: P1 → P2
Target Milestone: 3.4 → 4.0
Changed the QA contact to Bishakha.
QA Contact: sonja.mirtitsch → bishakhabanerjee
QA Contact: bishakhabanerjee → jason.m.reid
Taking bug. Note that the recovery code has been moved to a new source file: cmd/dbck/dbrecover.c
Assignee: bugz → nelson
Priority: P2 → P3
Target Milestone: 4.0 → ---
QA Contact: jason.m.reid → tools
Assignee: nelson → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.