Comment by tomsonj

3 days ago

chisel is a similar tool in this space https://github.com/jpillora/chisel

I don’t get why headers and requests need to be spoofed if all traffic is over https?

11 comments

tomsonj

Reply
mhio  3 days ago

The headers are seen by the monster-in-the-middle CDN.

It's obfuscation at best. I'm not sure the encrypted traffic will look particularly php-ish for example. Compressed formats might look vaguely passable.

I can't see any stenography code or libraries in the repo.

duskwuff  3 days ago

> I don’t get why headers and requests need to be spoofed if all traffic is over https?

Because the traffic is to a CDN endpoint (like Cloudflare) which expects it to be a HTTP message.

  • tomsonj  2 days ago

    it can still be an https message, who cares what the path, query string, or headers look like? that is all encrypted

coretx  3 days ago

Because SNI. Also, State (sponsored) Actors are certificate authorities. HTTPS is the biggest scam in internet history. https://en.wikipedia.org/wiki/Server_Name_Indication

  • astrange  3 days ago

    This certainly was an issue but it's solved by ECH/DoH. As long as they aren't blocked on your network anyway.

    > Also, State (sponsored) Actors are certificate authorities.

    To generate a fake certificate as a CA you have to either put it in the Certificate Transparency log, in which case everyone will notice, or don't, in which case browsers will notice (they know what top sites' certificates are supposed to look like) and your CA will get shut down.

    • hamilyon2  3 days ago

      Someone should really test it, real red team black hat style and then fully publish the results. Try to mitm https with real unlogged certs and see what happens. Preregister the whole fully detailed procedure on blockchain. And report to public results fully, with proofs of being caught.