If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Intermittent failure: TLS 1.0 Request don't require client auth on 2nd hs (bad password)

REOPENED
Unassigned

Status

NSS
Test
REOPENED
5 years ago
4 years ago

People

(Reporter: briansmith, Unassigned)

Tracking

trunk
x86
Windows 7

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Created attachment 686404 [details]
Build log (gzipped html)

Looks similar to bug 540513.

ssl.sh: TLS 1.0 Request don't require client auth on 2nd hs (bad password) ----
selfserv starting at Sat Nov 24 17:13:48 EST 2012
selfserv -D -p 8544 -d ../server -n buildnss05.localdomain  \
         -e buildnss05.localdomain-ec -w nss -r -r -r -i ../tests_pid.5420  &
trying to connect to selfserv at Sat Nov 24 17:13:49 EST 2012
tstclnt -p 8544 -h buildnss05.localdomain  -q \
        -d ../client -v < /c/mozilla-build/msys/tinderbox/tinderlight/data/buildnss05_trunk_64_OPT/mozilla/security/nss/tests/ssl/sslreq.dat
tstclnt.exe: connecting to buildnss05.localdomain:8544 (address=127.0.0.1)
kill -0 4188 >/dev/null 2>/dev/null
selfserv with PID 4188 found at Sat Nov 24 17:13:49 EST 2012
selfserv with PID 4188 started at Sat Nov 24 17:13:49 EST 2012
tstclnt -p 8544 -h buildnss05.localdomain -f -d ../client -v \
        -V ssl3:tls1.0 -w bogus -n TestUser40  < /c/mozilla-build/msys/tinderbox/tinderlight/data/buildnss05_trunk_64_OPT/mozilla/security/nss/tests/ssl/sslreq.dat
tstclnt.exe: connecting to buildnss05.localdomain:8544 (address=127.0.0.1)
tstclnt.exe: connect: Operation is still in progress (probably a non-blocking connect)
tstclnt.exe: about to call PR_Poll for connect completion!
tstclnt.exe: PR_Poll returned 0x02 for socket out_flags.
tstclnt.exe: ready...
tstclnt.exe: about to call PR_Poll !
tstclnt.exe: PR_Poll returned!
tstclnt.exe: PR_Poll returned 0x01 for stdin out_flags.
tstclnt.exe: PR_Poll returned 0x00 for socket out_flags.
tstclnt.exe: stdin read 18 bytes
tstclnt.exe: Writing 18 bytes to server
tstclnt.exe: about to call PR_Poll on writable socket !
tstclnt.exe: PR_Poll returned with writable socket !
tstclnt.exe: using asynchronous certificate validation
tstclnt.exe: handshake was paused by auth certificate hook
tstclnt.exe: about to call PR_Poll on writable socket !
tstclnt.exe: PR_Poll returned with writable socket !
tstclnt.exe: write to SSL socket failed: SSL peer reports incorrect Message Authentication Code.
tstclnt: exiting with return code 254
ssl.sh: #960: TLS 1.0 Request don't require client auth on 2nd hs (bad password) (cert TestUser40 - revoked) produced a returncode of 254, expected is 0 - FAILED

[...]

Tests summary:
--------------
Passed:             8494
Failed:             1
Failed with core:   0
Unknown status:     0
See Also: → bug 370626

Comment 1

5 years ago
Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of:
{random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open}

There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME

Comment 2

5 years ago
Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of:
{random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open}

There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---

Updated

4 years ago
Keywords: intermittent-failure
You need to log in before you can comment on or make changes to this bug.