Open Bug 390184 Opened 18 years ago Updated 3 years ago

signtool fails when nickname contains colon, reports no more directory entries

Categories

(NSS :: Libraries, defect, P3)

Tracking

(Not tracked)

People

(Reporter: nelson, Unassigned)

References

(Depends on 1 open bug)

Details

This bug in an "umbrella" bug, acting to tie together numerous other bug reports that I will soon file. In mozilla.dev.tech.crypto, someone reported that the command signtool -d . -k "PvkTmp:99ace907-0a0c-4066-bd60-751431d09f92 " \ -p "passw" signed gave the following output: using certificate directory: . Generating signed//META-INF/manifest.mf file.. --> install.rdf --> Plugins/NPSoda.dll Generating zigbert.sf file.. signtool: the cert "PvkTmp:99ace907-0a0c-4066-bd60-751431d09f92" does not exist in the database: No more entries in the directory. the tree signed/ was NOT SUCCESSFULLY SIGNED. There are numerous problems shown by that output, including: a) failure to find a cert whose nickname contains a colon. (Such names may legitimately exist, and PSM can now select them, after bug 251594, but signtool and some other NSS commands still cannot.) b) reporting "does not exist in the database", when it did not search the database AT ALL, and c) reporting "No more entries in the directory." when it did not encounter any problem with file names in directories. This is due to failure to set an error code in PK11_FindCertFromNickname, and in the functions it calls. I will soon file bugs about all the issues, and mark them as blockers of this bug.
Priority: -- → P3
Depends on: 390185
Depends on: 390187
Depends on: 390188
Depends on: 390189
Depends on: 390191
Target Milestone: --- → 3.12
Unsetting target milestone in unresolved bugs whose targets have passed.
Target Milestone: 3.12 → ---
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.