Netgear Signed TLS Cert Private Key Disclosure

Re:Netgear Signed TLS Cert Private Key Disclosure by vbezhenar on Monday January 20, 2020 @04:46AM (#22097682)

Yeah, that's why I think that movement to HTTPS everywhere must at least exclude private IP addresses. While it's expected to have HTTPS on public resources, what happens in my local network is my business and should not be considered insecure.

[ Parent | on HN ]

Re:Netgear Signed TLS Cert Private Key Disclosure by ajsnigrutin on Monday January 20, 2020 @07:35AM (#22098359)

The problem is, that someone setting up a public wifi (in a restaurant for example), will be vulnerable to sniffing attacks (if they don't know what they're doing).

[ Parent | on HN ]

Re:Netgear Signed TLS Cert Private Key Disclosure by franga2000 on Monday January 20, 2020 @08:22AM (#22098588)

So get a cert before setting up wifi. This is not a hard problem. 1. Connect to AP with random key from the box 2. Open admin panel over HTTP 3. Follow instructions to get Internet access 4. As soon as it has a connection, the router obtains a cert and redirects you to HTTPS 5. Now you can make all your poor security decisions

[ Parent | on HN ]

Re:Netgear Signed TLS Cert Private Key Disclosure by Terretta on Monday January 20, 2020 @10:44AM (#22099586)

Have you met ‘normals’?

Everything is a hard problem if it’s any steps at all.

[ Parent | on HN ]

Re:Netgear Signed TLS Cert Private Key Disclosure by franga2000 on Monday January 20, 2020 @11:03AM (#22099733)

I meant that "how to make router setup secure without making it more difficult" is not a hard problem. My system is no more difficult than the currently most common ones and about as secure as it gets.

Although, one could argue that setting up a router really shouldn't be left to people who don't understand how they work...

[ Parent | on HN ]