Closed Bug 1105527 Opened 10 years ago Closed 10 years ago

Error code: sec_error_invalid_key

Categories

(Firefox :: Untriaged, defect)

33 Branch
x86_64
Linux
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1084606

People

(Reporter: dian, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141013200257

Steps to reproduce:

Point your Firefox 33.0 to a self signed cert wifi router that was working before (earlier ver og Firefox allowed an exception to be added).
Get this new error:
Just upgraded to 33.0 and I get this error:
Secure Connection Failed
An error occurred during a connection to 192.168.2.1. The key does not support the requested operation. (Error code: sec_error_invalid_key)
___
my local router is with a self signed cert - what could possible be a security concern here and why should I pay Verisign $$ for a recognised cert, to make Firefox 33.0 work with my router that has been working for years?!?
Can you please fix this? This is ridiculous...


Actual results:

Secure Connection Failed
An error occurred during a connection to 192.168.2.1. The key does not support the requested operation. (Error code: sec_error_invalid_key)
[no option to add an exception] - why?!? - this was woring in prev. versions...


Expected results:

option to add an exception - this was working in prev. versions...
Severity: normal → critical
This should be fixed in 34.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.