Closed Bug 77511 Opened 24 years ago Closed 24 years ago

I can't view https pages

Categories

(Core Graveyard :: Security: UI, defect)

1.0 Branch
x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: amateo, Assigned: ddrinan0264)

Details

Every time I try to enter in a secure web, I get the error: "The connection was refused when attempting to contact www.domain". I have tried to enter in Tasks->Privacy and Security->Personal Security Manager but I can't, and I get the error: Error: uncaught exception: [Exception... "Component returned failure code 0x80004005 (NS_ERROR_FAILURE) [nslSecurityManagerComponent.displaySecurityAdvisor]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame:: chrome://communicator/content/PSMTaskMenu.xul :: displaySecurityAdvisor :: line 12" data: no]
Reporter: Which build are you using ? (Include in every bug report the build ID) Have you a CVS build or a nightly from ftp.mozilla.org ? If you have a CVS build, have you also build PSM2 ? "Tasks->Privacy and Security->Personal Security Manager" is dead. You can see the the settings in the normal Preferences/security. (since PSM2)
I believe this is security: crypto. Please change back if you disagree.
Assignee: mstoltz → ddrinan
Component: Security: General → Security: Crypto
QA Contact: ckritzer → junruh
sorry, the build is 2001021712. I have installed it from a rpm package, from mozilla-0.8.2 rpm package.
Marking invalid. The lastest builds reach https sites. Reporter, please use the nightly build for testing. http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-i686-pc-linux-gnu.tar. gz
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Verified.
Status: RESOLVED → VERIFIED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
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.