Closed
Bug 62946
Opened 24 years ago
Closed 24 years ago
connection refused to secure site
Categories
(SeaMonkey :: Build Config, defect, P3)
SeaMonkey
Build Config
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
Assignee | ||
Comment 1•24 years ago
|
||
this will keep us from opening the tree.
Comment 2•24 years ago
|
||
This may be a packaging problem. Is there a psm.exe and psmdata bundled with the commercial build on Windows?
Assignee | ||
Comment 3•24 years ago
|
||
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.
Comment 4•24 years ago
|
||
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 .
Assignee | ||
Comment 5•24 years ago
|
||
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
Assignee | ||
Updated•24 years ago
|
Severity: blocker → critical
Assignee | ||
Comment 7•24 years ago
|
||
reducing severity to drop off radar.
Reporter | ||
Comment 9•24 years ago
|
||
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
Comment 10•24 years ago
|
||
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
Reporter | ||
Comment 11•24 years ago
|
||
verified fixed linx commercial build 2000-12-26-10-mtrunk
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 12•24 years ago
|
||
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 → ---
Assignee | ||
Comment 13•24 years ago
|
||
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
Comment 14•24 years ago
|
||
today's problem is PSM not building at all; i think that qualifies as a different bug.
Comment 15•24 years ago
|
||
Hm, that doesn't look like PSM code breakage. Someone remind where the logs for the nightlies live.
Assignee | ||
Comment 16•24 years ago
|
||
/u/cltbld/logs. I renamed the log make_moz.linux22.javi so it won't be automatically deleted by the next build.
Comment 17•24 years ago
|
||
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?
Reporter | ||
Comment 18•24 years ago
|
||
working okay on linux commercial build 2001-02-22-13-mtrunk
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 19•24 years ago
|
||
veirfied on linux commercial builld 2001-02-26-05-mtrunk
Status: RESOLVED → VERIFIED
Comment 20•24 years ago
|
||
*** Bug 69987 has been marked as a duplicate of this bug. ***
Comment 21•24 years ago
|
||
*** Bug 69987 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•