Closed
Bug 123147
Opened 23 years ago
Closed 23 years ago
Reporting error -12227 after failed SSL negotiation.
Categories
(Core Graveyard :: Security: UI, defect, P1)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
psm2.2
People
(Reporter: lars, Assigned: rangansen)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8+) Gecko/20020131 BuildID: 2002013100 On an internal web server, Mozilla is reporting "<server> has received an incorrect or unexpected message. Error code = -12227". Netscape, links, lynx, and curl are all able to successfully negotiate an SSL connection with this server. Maybe this is really a simple problem; I don't know what error -12227 is. Reproducible: Always Steps to Reproduce: I'm using a local CA to create the SSL certificate for the server. The CN in the certificate does not match the hostname that I'm currently using to connect to the server.
Comment 1•23 years ago
|
||
-> PSM
Assignee: asa → ssaux
Component: Browser-General → Client Library
Product: Browser → PSM
QA Contact: doronr → junruh
Version: other → unspecified
Comment 2•23 years ago
|
||
rangan. SSL_ERROR_HANDSHAKE_FAILURE_ALERT "SSL peer was unable to negotiate an acceptable set of security parameters." This is more meaningfull that what the error is currently. I'm starting to believe that we should have all the errors shown. Reporter. Obvisously without having access to a public server displaying this error we can't really debug this, if it's a bug. You may have turned off some cyphers/protocol. Both client and server have to agree when negotiating the handshake. The fact that other clients agree with this server may just mean that they're less strict (and therefore probably less secure).
Assignee: ssaux → rangansen
Priority: -- → P1
Target Milestone: --- → 2.2
I will try generating a new key and if that has the same problem I'll attach the csr and certificate here.
Comment 4•23 years ago
|
||
Reporter, are you still seeing a problem?
Comment 5•23 years ago
|
||
Marking works for me. Reporter, try a new profile, and if you are still having problems, reopen this bug and try to include as much detail as possible.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•