489989 - Signtool failed with unknown reason.

Status: RESOLVED DUPLICATE of bug 485145

(NSS :: Tools, defect)

Description

[Slavomir Katuscak]

This failure occured on Windows Tinderbox:
goride MINGW32_NT-5.2 32bit OPT on 2009/04/23 21:47:55

Failrue occured in Upgrade DB cycle where databases were upgraded from old format to SQL (both formats were presented).

Signtool failed with unknown reason:

tools.sh: Listing signed files in jar ----------------------
signtool -v nojs.jar -d ../alicedir -p nss -k objsigner
tools.sh: #5436: Listing signed files in jar (signtool -v)  - FAILED

Output of this tests should be:

tools.sh: Listing signed files in jar ----------------------
signtool -v nojs.jar -d ../alicedir -p nss -k objsigner
archive "nojs.jar" has passed crypto verification.

          status   path
    ------------   -------------------
        verified   sign.html
        verified   signjs.html
tools.sh: #6622: Listing signed files in jar (signtool -v)  - PASSED

There was no visible failure, signtool doesn't print anything on output, but exit value comparison failed, so there was no 0 on exit. I tried to run this command manually, with old DB format I got on output that archive did not pass crypto verification, this is OK because it was in upgrade DB cycle, when I set NSS_DEFAULT_DB_TYPE to value sql to use correct DB, result was OK and verification passed.

Comment 1

[Nelson Bolyard (seldom reads bugmail)]

This is one of the symptoms of the problem previously documented in bug 485145.
If this problem recurs after bug 485145 is fixed, then this can be reopened.