Open Bug 1483113 Opened 7 years ago Updated 1 years ago

Add a integrity_check for nssdb

Categories

(NSS :: Libraries, enhancement, P5)

Product:
NSS
Component:
Libraries
Version:
3.23
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: su.g.kim, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce: We are embedding Mozilla's root store, especially NSS libs in our products. And I found out there is no recovery logic in case nssdb is corrupted. I corrupted the nssdb (cert9.db / key4.db) forcibly by modifying it with hexa editor like HxD. Actual results: With corrupted db, certificate files was not added into the nssdb and even if I reboot the devices, nssdb was not recovered. Expected results: NSS should check the status of nssdb, If they have some problem, It need to be recovered itself or let the caller know the status of nssdb.
I'm working on it. Please assign it to me.
Severity: normal → S3
Assignee: nobody → su.g.kim
Severity: S3 → S4
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Priority: -- → P5

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Assignee: su.g.kim → nobody
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.