Secure Connection Failed - 192.168.1.1

[s|b]

I want to connect to my router (Cisco/Linksys E2000 with DD-WRT
installed) and I'm getting this message:

| Secure Connection Failed
|
| An error occurred during a connection to 192.168.1.1. The key does not support the requested operation. (Error code: sec_error_invalid_key)
|
| The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
| Please contact the website owners to inform them of this problem.
|
| Try Again

In the past, I would create an exception and it would work, but since
33.x this doesn't work anymore. From what I understand, this is now
"normal" behaviour to increase security. That's all fine, but I want to
be able to access my router, not with IE (which still works), but with
Fx and without downgrading. Is there a way this can be done?

--
s|b

[Dave Royal]

It may be related to this, which was fixed in v33:
<https://bugzilla.mozilla.org/show_bug.cgi?id=1045973#c37>

I raised a similar (but different) bug (1044441) when I couldn't access a
wireless AP. In that case it was fixed by ignoring the technically-
invalid certificate. I suggest you raise a bug for your case.

[Keith Nuttle]

Have you changed your router's address? While I have not had many
routers, they all defaulted to 192.168.0.1.

I just accessed my router using the address 192.168.0.1, but if I try
using 192.168.1.1, I get an error similar to what you got.

[s|b]

On Sat, 25 Oct 2014 12:16:16 -0400, Keith Nuttle wrote:

> Have you changed your router's address? While I have not had many
> routers, they all defaulted to 192.168.0.1.

I wish it were so simple, but I'm 200% sure of the address. I already
stated it still works with IE, so...

--
s|b

[s|b]

On Sat, 25 Oct 2014 10:39:10 -0500, Dave Royal wrote:

> It may be related to this, which was fixed in v33:
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1045973#c37>

I did a search before posting my message and from what I found, this is
not a bug, but more a security issue. I can access the address with
32.x, but only if I add an exception, something that isn't possible
anymore in 33.x.

I tried accessing with a portable Fx 34.x Beta, but that did work
either. :-(

--
s|b

[s|b]

On Sat, 25 Oct 2014 14:29:45 +0200, s|b wrote:

> I want to connect to my router (Cisco/Linksys E2000 with DD-WRT
> installed) and I'm getting this message:
>
> | Secure Connection Failed
> |
> | An error occurred during a connection to 192.168.1.1. The key does not support the requested operation. (Error code: sec_error_invalid_key)

I tried something else. I was trying to access through HTTPS and when I
tried HTTP it jumped to HTTPS anyway. Then I remembered I set up
NoScript to force Fx to use a secure connection for 192.168.1.1. I
unchecked this, accessed the router with IE to make it possible to use
HTTP (this was disabled) and now I'm able to access it again with Fx.

I would still like to know how to use a secure connection with Fx
though...

--
s|b

[Dave Royal]

I also found this
<https://bugzilla.mozilla.org/show_bug.cgi?id=1084606>

[Christian Riechers]

See https://bugzilla.mozilla.org/show_bug.cgi?id=1084606
It's possibly due to the 512 bit key size.
Comment on the bug if there's new information you can contribute.
Otherwise 'me too' kind of comments or rants are useless.

--
Christian

[s|b]

On Sat, 25 Oct 2014 12:01:45 -0500, Dave Royal wrote:

> I also found this
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1084606>

Yes, that's one of the search results I came across. I see Christian
also refers to it.

--
s|b

[s|b]

On Sat, 25 Oct 2014 19:12:50 +0200, Christian Riechers wrote:

> See https://bugzilla.mozilla.org/show_bug.cgi?id=1084606
> It's possibly due to the 512 bit key size.

It's one of the search results I came across.

> Comment on the bug if there's new information you can contribute.
> Otherwise 'me too' kind of comments or rants are useless.

I don't have an account and I don't feel like creating one just yet.

But while I'm writing this I tried to access the router again through
HTTPS and I got the familiar text about adding an exception. I added the
exception and now it works again. :-???

--
s|b

[Ron Hunter]

Check the manual. Various companies use different IP numbers for the
router. Try 192.168.0.1 or 192.168.0.0

[Robert Bee]

Hmm, I found that in the Config editor I'd set
security.tls.version.min=1 from a value of zero to try to make FF more
secure following a recommendation from somewhere.

When I changed this value back to zero, hey presto I could access the
router again. I should add that I use https://192.168.1.1 to get to my
router.

[Nobody]

Hmm, I found that in the Config editor I'd set
security.tls.version.min=1 from a value of zero to try to make FF more
secure following a recommendation from somewhere.

When I changed this value back to zero, hey presto I could access the
router again. I should add that I use https://192.168.1.1 to get to my
router.


On Sat 25/10/2014 19:46, s|b wrote:

[Dave Warren]

In the last episode of
<mailman.1499.141427227...@lists.mozilla.org>, Ron

Hunter <rphu...@charter.net> said:

>Check the manual. Various companies use different IP numbers for the
>router. Try 192.168.0.1 or 192.168.0.0

I doubt you'll find many using 192.168.0.0 since this normally isn't a
valid IP for a /24 (or even a /16). 192.168.0.1 was the traditional
default, although some manufacturers use others.

[s|b]

On Sun, 26 Oct 2014 00:19:50 +0100, Nobody wrote:

> Hmm, I found that in the Config editor I'd set
> security.tls.version.min=1 from a value of zero to try to make FF more
> secure following a recommendation from somewhere.
>
> When I changed this value back to zero, hey presto I could access the
> router again. I should add that I use https://192.168.1.1 to get to my
> router.

security.tls.version.min=1 is set to 1.

--
s|b

[»Q«]

In
<news:mailman.1550.141434818...@lists.mozilla.org>,

I'd set it to 0 *only* long enough to configure the router, then change
it back to 1.

AIUI, the value of 1 prevents fallback to SSL v3. They're talking
seriously about removing SSL v3 support from Firefox entirely. Once
they do, I guess it just won't be possible to access your router with
Firefox.