Closed Bug 41680 Opened 24 years ago Closed 24 years ago

Linux - Cannot connect to a secure site

Categories

(Core Graveyard :: Security: UI, defect, P1)

1.0 Branch
Other
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: junruh, Assigned: pavlov)

References

()

Details

(Keywords: smoketest, Whiteboard: [dogfood+][nsbeta2-][M16Blocker])

Just tested again with 2000060608/Linux and get the error message "The
connection was refused when trying to contact <server>" Browser hasn't crashed
yet but still unable to access secure pages.
Assigning to javi.
Assignee: dougt → javi
Keywords: smoketest
Priority: P3 → P1
Target Milestone: --- → M16
PSM expired June 01 (says so too on the iplanet site). Means, it will not
connect to any secure site.  Is this a invalid bug or do you have a new version
of PSM?

Huh?

Which build? Commercial or Mozilla?  Did you try installing the bits on 
johngalt.red.iplanet.com?
I am testing the commercial build. Before and after installing PSM from 
http://johngalt.red.iplanet.com/docs/manuals/psm/psm-mozilla/index.html I get 
the same non-connect to an https site result. Also, the Security Advisor does 
not open.
I agree with John, I did the same and stil cannot get PSM to function.
Keywords: dogfood, nsbeta2
*** Bug 40349 has been marked as a duplicate of this bug. ***
Putting on [dogfood+][M16Blocker] radar.
Whiteboard: [dogfood+][nsbeta2-][M16Blocker]
Downloading the new PSM bits at 
http://docs.iplanet.com/docs/manuals/psm/psm-mozilla/index.html will fix this.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Will verify when the bits are in the commercial build - hopefully 6/7.
Commercial build only, so not an M16 blocker.
adding self to cc list, and wondering why bug 40349 (earlier bug) was made a
dupe of this one...
nope, still a problem using opt commercial bits 2000.06.07.10. reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This worksforme with the 2000-06-08-08-M17 linux commercial build. I can 
connect to https://digitalid.verisign.com/, launch the psm ui, and get the 
'locked' security UI when I'm on this secure page. 

However, I do note that going to https://www.verisign.com/ produces an alert
about mixed content (secure/insecure), and is _extremely_ slow to load. That
though may be a different bug.
Marking fixed.
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
I reproduced this bug on Mac comm. 2000-06-16-08-M17
Status: VERIFIED → REOPENED
OS: Linux → Mac System 9.0
Resolution: FIXED → ---
RE-assigning to Patrick since he's working on Mac PSM.
Assignee: javi → beard
Status: REOPENED → NEW
Still happening on 2000061611/Linux. I don't thin it ever worked for me.
My Mac + PSM build works just fine. on both of these URLs. Reassigning to pavlov 
for a quick look.
Assignee: beard → pavlov
adding Samir to the CC: list in case me might know something.
Is it necessary to download a special PSM patch or build in order to connect to
a secure site? Cuz I'm just downloading regular nightly builds with nothing
added...
Oh... I would think this is an important enough feature that it would be
included in the nightly builds :-\ I guess there must be a reason not to...
Marking fixed. This is not a Mac bug. There is no crypto available on Mac yet. 
For Linux, go to the bottom of the page at 
http://docs.iplanet.com/docs/manuals/psm/psm-mozilla/ and click on th button 
that says Install PSM for Linxu to add crypto to Linux.
Status: NEW → RESOLVED
Closed: 24 years ago24 years ago
OS: Mac System 9.0 → Linux
Resolution: --- → FIXED
Target Milestone: M16 → M17
verified.
Status: RESOLVED → VERIFIED
This is still happening with the most recent mozilla build in solaris
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Target Milestone: M17 → ---
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.