Closed
Bug 148860
Opened 22 years ago
Closed 5 months ago
complete, precise documentation of certificate management API
Categories
(NSS :: Documentation, enhancement, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jamie-bugzilla, Unassigned)
Details
This is a requirement for the cert API. The comments in the PKI header files are a good start, but I need deeper explanations. Essentially, the documentation for each function should explain: 1. What the function will return, for every possible configuration of certificate and key databases and PKCS #11 modules. Obviously you can't enumerate all possible configurations. What I'm looking for are very precise definitions. For example, a function to find a certificate by nickname could say "This function will iterate across all PKCS #11 modules. On each module, it will issue a search for all certificate objects whose CKA_LABEL attribute equals the given nickname. The function will return a list containing all the certificates found by these searches." 2. How the function will change the state of the certificate and key databases and PKCS #11 modules. For example, there are currently several functions for importing certificates in the database, and they are all subtle (if a certificate is imported whose private key lives on a PKCS #11 hardware token, will a copy of the certificate also be placed in cert7.db?) These sorts of questions should be answerable by reading the documentation, without having to read the code.
Comment 1•21 years ago
|
||
Enhancement request, Requesting new documentation.
Severity: major → enhancement
Priority: -- → P2
Updated•18 years ago
|
Assignee: wtchang → nobody
QA Contact: wtchang → documentation
Updated•2 years ago
|
Severity: normal → S3
Updated•5 months ago
|
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•