Closed Bug 62946 Opened 24 years ago Closed 24 years ago

connection refused to secure site

Categories

(SeaMonkey :: Build Config, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: tracy, Assigned: granrosebugs)

References

()

Details

(Keywords: smoketest)

seen on linux commercial build 2000-12-15-06-Mtrunk

-attempt to load listed URL
-after closiing the normal security warning window an alert window appears " The 
 connection was refused when attempting to contact digitalid.verisign.com"
-click okay to this window

the lock icon in lower right of browser window turns red with the lock broken
Keywords: smoketest
this will keep us from opening the tree.
This may be a packaging problem.

Is there a psm.exe and psmdata bundled with the commercial build on Windows?
This is linux.

I do not see this problem with the tarball, but do see it with the installer
build, so it looks like a packaging problem.  When I install I get an error -621
that a xpi file failed to install, but I do not see an install log anywhere
saying what xpi it failed on.  Doing a find for *psm* only shows libpsmglue
which indicates that psm did not get installed.  I'll take a look at the build
logs to see if I can see any errors.

cc'ing sgehani for his expertise.
The changes to get PSM to build as part of the Linux Mozilla builds haven't
landed, so the old way of putting in PSM via the xpi still applies for Linux via
commercial builds.

The bug to get PSM building as part of the Linux mozilla builds is 60912, when
that lands, then there will have to be some packaging changes made to the
commercial and mozilla builds .
IS f*cked us again for the third time this month, without any warning
whatsoever.  They moved the NFS share we use to store our third party
components.  This means no java, no PSM, no anything that isn't in CVS.

Taking bug, reassigning QA to leaf, changing to build config.
Component: Security: Crypto → Build Config
QA Contact: junruh → leaf
taking bug.
Assignee: ddrinan → granrose
Severity: blocker → critical
reducing severity to drop off radar.
*** Bug 62948 has been marked as a duplicate of this bug. ***
Depends on: 62738
No longer depends on: 62738
commercial builds:

windows 2000-12-18-06-Mtrunk
linux 2000-12-18-06-Mtrunk

able to access secure site now, but the lock is showing broken on linux and 
unlocked on windows
OS: Linux → All
Hardware: PC → All
mac and windows are working with psm in the tree, the linux mozilla bits don't
have security in them yet, and the commercial bits should have problems filed in
bugscape.

The broken/unlocked lock is probably a result of mixed content, because it works
for me on https://despot.mozilla.org.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
verified fixed linx commercial build 2000-12-26-10-mtrunk
Status: RESOLVED → VERIFIED
seeing this again on linux commercial build 2000-02-22-06-mtrunk

bug 62948 is happening again...it was orginally duped of this bug, so I left it 
closed. But I am reopening this bug because I believe that is the file that is 
failing to load.  Can't access a secure site
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
this is probably a different bug, but PSM failed to build in the linux build
this morning:

gmake[1]: Leaving directory
`/builds/client/linux22/seamonkey/mozilla/layout/base/public'
gmake[1]: Entering directory
`/builds/client/linux22/seamonkey/mozilla/rdf/content/public'
gmake[1]: *** No rule to make target `export'.  Stop.
gmake[1]: Leaving directory
`/builds/client/linux22/seamonkey/mozilla/rdf/content/public'
gmake: *** [export] Error 2
today's problem is PSM not building at all; i think that qualifies as a 
different bug.
Hm, that doesn't look like PSM code breakage.  Someone remind where the logs for
the nightlies live.
/u/cltbld/logs.  I renamed the log make_moz.linux22.javi so it won't be
automatically deleted by the next build.
Seems that someone removed some Makefiles from the tree and didn't update the
MAKEFILES_psm_glue entry in allmakefiles.sh

Any idea who would know off the bat which makefiles to remove/add to maintain
prior functionality?
working okay on linux commercial build 2001-02-22-13-mtrunk
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → WORKSFORME
veirfied on linux commercial builld 2001-02-26-05-mtrunk
Status: RESOLVED → VERIFIED
*** Bug 69987 has been marked as a duplicate of this bug. ***
*** Bug 69987 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.