Closed Bug 125524 Opened 23 years ago Closed 23 years ago

Cannot use HTTPS, browser reports PSM must be installed

Categories

(SeaMonkey :: Build Config, defect)

x86
FreeBSD
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 124211

People

(Reporter: jf, Assigned: netscape)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.8+) Gecko/20020214
BuildID:    2002021407

When trying to access HTTPS pages, a popup window with the following text appears:

This document cannot be displayed unless you install the Personal Security
ManagerPSM).
Download and install PSM and try again, or contact your system administrator.


Reproducible: Always
Steps to Reproduce:
1. Go to http://play.com/
2. Click on "Log In" button under "Your Account"

(In fact, connecting to any HTTPS site will show this behaviour.)



Actual Results:  This popup appears:

This document cannot be displayed unless you install the Personal Security
ManagerPSM).
Download and install PSM and try again, or contact your system administrator.

Expected Results:  The secure page should be displayed.

I first discovered this problem on February 11 after having CVS-updated my tree
for the first time in over a week. I do have "--enable-crypto" in configuration
statement.

Tried removing the tree and pulling it again. Same problem.
Tried removing my ~/.mozilla directory. Same problem.

I then tried downloading the latest nightly in binary form and this is also
having a problem.

During the build, there are often lines displayed around the security components
of "There are no private exports." - I do not have the output of an earlier
build so I do not know whether this was also seen before.
this looks very much like bug 123964.  PSM changes were not repackaged properly
for mac OSX...perhaps that's what is happening here?
sounds like build config
Assignee: mstoltz → seawood
Component: Security: General → Build Config
QA Contact: bsharma → granrose
Sounds suspiciously like bug 124211 .  Jens, do you see any output to the
console when you first start up Mozilla or run regxpcom?  You may have to remove
component.reg to see the messages again.

I just deleted my component.reg and tried to start Mozilla from the command line
(usually I do it from a desktop link so I do not see the output). This is what I
get:


dilbert:~$ mozilla
**************************************************
nsNativeComponentLoader:
SelfRegisterDll(/usr/X11R6/lib/mozilla/components/libpipnss.so) Load FAILED with
error: Cannot open "../../../../dist/lib/libsmime3.so"
**************************************************
*** Deferring registration of sample JS components
*** Registering -venkman handler.
*** Registering smime account manager extension.
*** Registering sample JS components


If I close it and restart it, I still get error message between the asterisk lines.

But yes, this certainly does look a lot like bug 124211.


[On a side note, IRC seems to be affected as well. This is not listed or offered
as an option inside Mozilla; however it works fine in the nightly I downloaded
so it may be unrelated.]

*** This bug has been marked as a duplicate of 124211 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
vrfy dupe
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.