Closed Bug 171930 Opened 22 years ago Closed 22 years ago

encrypted content is invalid or corrupt. error code -8101

Categories

(Core Graveyard :: Security: UI, defect)

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: genanr, Assigned: ssaux)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021001 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021001 I get the message Could not establish an encrypted connection because certificate presented by secure.instacontent.net is invalid or corrupted. Error code -8101 This link works in IE and Netscape 4.7 Reproducible: Always Steps to Reproduce: 1. Just go to the link listed 2. 3. Actual Results: I get the message Expected Results: accept the certificate (unless instacontent really is wrong)
Security General != encrypted connections -> PSM (for duping)
Assignee: mstoltz → ssaux
Component: Security: General → Client Library
Product: Browser → PSM
QA Contact: bsharma → junruh
Version: other → unspecified
Works for me. Reporter, can you try a new profile? "./mozilla -ProfileManager". Your certifice DB may be corrupted.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Error still occures even after creating a new profile. Error also occures on another users machine using mozilla under windows. So the OS and profile are not the problem.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
error code -8101 is "Certificate type not approved for application." I cannot reproduce on Mac, Linux or Win2000. The cert is standard Verisign and the server is not TLS intolerant. VeriSign, Inc. VeriSign International Server CA - Class 3 www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign VeriSign Trust Network ssaux or kaie, do you have a problem reaching the test URL?
Version: unspecified → 2.4
I can not reproduce. Andy, do you have FIPS or OCSP enabled?
OCSP is not enabled FIPS compliant encryption is enabled
Confirming with FIPS enabled
Blocks: fips
Status: UNCONFIRMED → NEW
Ever confirmed: true
I am unable to reproduce this bug, regardless whether I have FIPS turned on or not. Note: Bug 172036 is another recent bug showing the same error message, and I can reproduce that other bug, but that other bug is independent of FIPS configuration. Not sure if these bugs are related.
I also get this bug whether FIPS is enabled or not
Works for me. I am unable to reproduce. Reporter, reopen if you can reproduce with a recent nightly build, and email me your prefs.js for inspection, please.
Status: NEW → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → WORKSFORME
V
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm2.4 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.