News for hackers. Stuff that matters.
Re:Public Key Pinning Extension for HTTP by notatoad on Tuesday October 28, 2014 @02:32PM (#8522621)
>The sslstrip problem seems impossible to make secure

I just do a 301 redirect to HTTPS on any requests that hit port 80. What makes that insecure?

Re:Public Key Pinning Extension for HTTP by jimktrains2 on Tuesday October 28, 2014 @02:47PM (#8522765)
A proxy could make the secure connection to the server and then feed the client an insecure one.

If the client has visited the server previously and obtained an HSTS header, it'll refuse to connect to make an insecure connection.

Re:Public Key Pinning Extension for HTTP by xorcist on Tuesday October 28, 2014 @03:05PM (#8522880)
It's not secure against traffic hijacking, where a malicious server would serve plaintext to the client and the average user would be none the wiser (no broken padlock).
Re:Public Key Pinning Extension for HTTP by notatoad on Tuesday October 28, 2014 @03:33PM (#8523064)
oh, of course. that makes sense. thanks.