Hide Forgot
Description of problem: 1. /mozilla/security/jss/org/mozilla/jss/ssl/SSLSocket.c:519 - Condition "addrBAelems == NULL" cannot be true as a result of line #502. 2. jss-4.2.6/mozilla/security/jss/org/mozilla/jss/ssl/common.c:152: Declaring variable "newFD" without initializer. jss-4.2.6/mozilla/security/jss/org/mozilla/jss/ssl/common.c:160 - Goto finish statement jss-4.2.6/mozilla/security/jss/org/mozilla/jss/ssl/common.c:281 - Using uninitialized value "newFD". Version-Release number of selected component (if applicable): 4.2.6-15 These defects were probably introduced by Red Hat patches.
*** Bug 722182 has been marked as a duplicate of this bug. ***
Created attachment 523908 [details] Patch for native coverity defects
Comment on attachment 523908 [details] Patch for native coverity defects Caveats: 1. Lines 1739-1744 Java_org_mozilla_jss_CryptoManager_verif You might want to initialize the derCerts array at the top using the array initializer technique. 2. Lines 564-570 static char* getPWFromConsole() What I believe they are complaining about is that you are assigning the output of "getchar", which returns an "int", into a variable of "char". This could result in data loss if the getchar is returning -1 or EOR or some such value.
The following email was sent to Release Engineering: Subject: Request to build 'JSS 4.2.6' on RHEL6 . . . Content: We would like to request an official build of 'jss-4.2.6-20.1.el6' on RHEL6 in Brew to address the following bugs: * Bugzilla Bug #733551 - DRM failed to recovery keys when in FIPS mode (HSM + NSS) * Bugzilla Bug #715621 - Defects revealed by Coverity scan The official spec files, source tarballs, other additional required sources, and all associated patches are located at: * http://pki.fedoraproject.org/pki/sources/jss/jss-4.2.6-20.el6/
New Coverity scan confirmed a fixation of mentioned defects in jss-4.2.6-20.el6.src.rpm.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1675.html