News for hackers. Stuff that matters.
Re:Firefox 36.0 released by JohnTHaller on Tuesday February 24, 2015 @10:30AM (#9101068)
For the curious, the duplicate SSL cert issue is in regards to some buggy routers and wireless printers with broken firmware. They send out invalid SSL certificates. Firefox doesn't have a way to provide an exception to allow access when security is compromised in this way but the user doesn't care and wants to access it anyway.

The only reason tabs generally misbehave is if Flash crashes. Firefox separates Flash out to a separate process so it won't crash the browser, even the tab the crashed Flash plugin is in. It just takes it a few more seconds than I'd like to realize the crash. (You can adjust the timing yourself, though). I haven't had a non-Flash-related Firefox issue in a very long time.

Re:Firefox 36.0 released by Karunamon on Tuesday February 24, 2015 @10:33AM (#9101088)
No, the certs are otherwise valid, but the problem is that once Firefox has seen a cert for a given address, if another address presents an identical cert, the second address cannot be browsed to without shutting down the browser and deleting the entire cert store.

Other offenders off the top of my head: BMC interface on Intel boards, HP iLO for blade management, F5 load balancers.

Yeah, they shouldn't be doing that, but the only thing being asked for here is a bleeding override button.

Re:Firefox 36.0 released by acdha on Tuesday February 24, 2015 @10:41AM (#9101167)
I find it curious that the people complaining about this don't instead install valid certificates. That was routine for us even a decade ago because otherwise you're literally training your admin staff to ignore errors and enter sensitive passwords every time a security warning pops up.

That's never good and it feels dangerously close to professional negligence when it's a password which gives privileged access to a server.

EDIT: just to be clear, I don't think this is “these people are crazy” so much as “what reason is good enough to justify leaving yourself exposed like this?” Even the cheap devices I bought in the early 2000s allowed you to install SSL certs and installing something real was a routine part of the first-time install.

Re:Firefox 36.0 released by mook on Wednesday February 25, 2015 @02:00AM (#9105639)
People probably don't install valid certificates because they can't. Consumer routers (think Linksys) are locked-down devices and things like SSL certificates are baked into the firmware. I'm curious what sorts of cheap devices you bought supported custom certificates; were they consumer-oriented? (That wasn't rhetorical; actually interested.)

Personally, I usually end up using plain unencrypted http instead, which is a net negative in terms of security (doesn't even protect against passive adversaries), but that seems to be what the SSL implementers prefer.

Re:Firefox 36.0 released by acdha on Wednesday February 25, 2015 @10:18AM (#9107083)
I've definitely run into consumer devices which allowed me to upload an SSL cert somewhere in the advanced settings but mostly I was thinking about the people on the bug commenting that their enterprise network, server management, etc. gear had bad certs. Even in the late 90s you could do this because .mil/.gov and many corporate purchasing contracts tended to require it.