bitslip · HackerTrans

Unrelated - I'm browsing this page right now over a proxy that's part of a project I'm working on in Haskell, using BearSSL for HTTPS. I can't of course speak to the correctness of the crypto primitives, but the project is small, self-contained, well written and easy to navigate such that writing the Haskell wrapper for it was relatively straight-forward. Great project.

bitslip

7 anni fadiscuss

For anyone reading this who isn't already familiar, the above is incorrect.

When you're browsing with HTTPS, a third party may see: - Your DNS queries (revealing the name of the website you're visiting),

- The handshake of your TLS connection, including Server Name Indicating (SNI) (revealing the name of the website you're visiting).

- A third party on the network is not however able to see the content of the website you're visiting, or the data you're submitting to the site.

When you're browsing with HTTP, a third party may see: - Your DNS queries (same as above)

- The name of the website you're visiting (via the host header)

- Any and all information sent between you and the website, as well as being able to modify any and all data sent between you and the website.

bitslip

7 anni fadiscuss

Not sure how genuine you're being, but there's a big difference between someone seeing the domain name of the website I'm visiting (publicdomainflix.com), and seeing my username and password when I register.

comments