Hacker News
The difficulty of making sure your website is broken
nottorp
|next
[-]
So I just ordered the cheapest AP I could find.
Except the damn device worked perfectly. Slow but rock solid.
One of our testers at $CURRENT_JOB also has trouble simulating a crap network, because our network is good.
paulirish
|next
|previous
[-]
ipython
|next
|previous
[-]
lifis
|next
|previous
[-]
bullen
|previous
[-]
Just "add your own crypto" on top, which is the ONLY thing a sane person would do.
3... 2... 1... banned?
horsawlarway
|root
|parent
|next
[-]
The payload that implements your crypto cannot be delivered over http, because any intermediate party can just modify your implementation and trivially compromise it.
If you don't trust TLS, you have to pre-share something. In the case of TLS and modern browser security, the "pre-shared" part is the crypto implementation running in the browser, and the default trusted store of root CAs (which lives in the browser or OS, depending).
If you want to avoid trusting that, you've got to distribute your algorithm through an alternative channel you do trust.