News for hackers. Stuff that matters.
Re:Last Call: HTTP2 by jacquesm on Thursday January 01, 2015 @08:58PM (#8825178)
https would stop injection just the same and is just http-over-ssl/tls. You could also simply sign the the content (but that would still allow wire-tapping).

Both still leave the original text based protocol and would stop ISP header injection.

Another defense against such trickery would be a legal one: make it illegal to tamper with data sent between two peers on the internet.

Imagine the postal service opening your mail and changing a couple of words in your mail just because they could.

Re:Last Call: HTTP2 by haberman on Thursday January 01, 2015 @09:06PM (#8825192)
> Both still leave the original text based protocol and would stop ISP header injection.

SSL is not a text-based protocol.

Re:Last Call: HTTP2 by jacquesm on Thursday January 01, 2015 @09:09PM (#8825200)
Neither is TCP, but that's just a wrapper.

Inside the SSL/TLS wrapper it is still just HTTP.

It's no longer 'in the clear' but it is still very much a text based protocol.

Re:Last Call: HTTP2 by haberman on Thursday January 01, 2015 @09:27PM (#8825251)
And HTTP2 is essentially just a multiplexed wrapper around HTTP1-like semantics, AFAICS.

I'm not an HTTP2 expert, but I would bet that WireShark can make an HTTP2 session look basically the same as a bunch of HTTP1 requests. It's the same "wrapper" concept except it adds multiplexing.

Re:Last Call: HTTP2 by MichaelGG on Thursday January 01, 2015 @11:32PM (#8825524)
Yeah and once you multiplex, your text based protocol is gonna suck to read anyways. So in practice you'll use Wireshark, and then you no longer care if it's text based.