Closed
Bug 40955
Opened 25 years ago
Closed 25 years ago
browser terminates on SSL links if PSM is not installed.
Categories
(Core Graveyard :: Security: UI, defect, P3)
Tracking
(Not tracked)
People
(Reporter: jim_nance, Assigned: dougt)
Details
If you do not install the psm stuff, visiting an ssl link will cause the browser
to die. Here is the code where it dies:
at /usr/local/home/jlnance/src/19980429/mozilla/extensions/psm-
glue/src/nsPSMShimLayer.c:74
74 PR_ASSERT(fd);
(gdb) n
76 }
(gdb)
84 sockopt.option = PR_SockOpt_NoDelay;
(gdb)
85 sockopt.value.no_delay = PR_TRUE;
(gdb)
86 rv = PR_SetSocketOption(fd, &sockopt);
(gdb)
87 PR_ASSERT(PR_SUCCESS == rv);
Comment 1•25 years ago
|
||
I don't know anything about SSL, but could this bug be related to (or even a
step towards a solution of) bug 40436 "Crashes at CMT_DestroyDataConnection"?
That bug is *the* current smoketest blocker, and when I try to visit an https://
site, I crash there.
Comment 2•25 years ago
|
||
Marking dup. See Comments From David Baron 2000-06-01 06:08 in bug 40436.
*** This bug has been marked as a duplicate of 40436 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 3•25 years ago
|
||
Oops. In bug 40436 there's a report about the assertion in line 87, while this
bug seems to be about the assertion in line 74. Is this a different bug then?
Comment 5•24 years ago
|
||
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Comment 6•24 years ago
|
||
Mass changing Security:Crypto to PSM
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•