News for hackers. Stuff that matters.
Re:Key compromise and root cert with exposed key in German l... by revelation on Sunday December 24, 2017 @11:43AM (#16000188)
They also asked users to import it into the Mozilla store, which (for mostly historically reasons) is separate. Feels like Mozilla should be revoking that specifically.

Ultimately, I have no idea what they are even trying to achieve here. If this is all localhost communication, HTTPS isn't doing anything.

Re:Key compromise and root cert with exposed key in German l... by mkup on Sunday December 24, 2017 @01:11PM (#16000527)
Probably they're trying to avoid "not secure" warnings from browser which are displayed if http-served web page contains password input fields (Chrome 56+, since October 2017).
Re:Key compromise and root cert with exposed key in German l... by mschuster91 on Sunday December 24, 2017 @03:10PM (#16001102)
These don't appear for localhost, though.
Re:Key compromise and root cert with exposed key in German l... by Xylakant on Sunday December 24, 2017 @04:35PM (#16001404)
It’s not localhost as domain, it’s a real registered domain that points to the loopback address.
Re:Key compromise and root cert with exposed key in German l... by revelation on Sunday December 24, 2017 @07:14PM (#16001969)
It should still not show the warning then, right? Because you're still talking to localhost, and that is ultimately what matters.

And what is the motivation behind having a domain you need internet for to resolve to point towards localhost to use with a certificate only localhost is meant to have? This is all sorts of effed up.

Re:Key compromise and root cert with exposed key in German l... by netsharc on Sunday December 24, 2017 @09:06PM (#16002258)
I'm guessing it's so the end-users can just say "go to www.[bla].de", similar to going to gmail.com...