search

sleeyax / burp-awesome-tls

Burp extension to evade TLS fingerprinting. Bypass WAF, spoof any browser.
GNU General Public License v3.0
991 stars 66 forks source link

HTTP2 SETTINGS iOS support #58

Open Aron148814 opened 5 months ago

Aron148814 commented 5 months ago

Will there be support for iOS? Because iOS devices only use MaxConcurrentStreams and InitialWindowSize.

Screenshot at Jan 25 14-36-46

sleeyax commented 5 months ago

I don't have an iOS device to test this myself at the moment so I would happily accept a PR for this feature!

Aron148814 commented 5 months ago

I fixed It by modifying some code in h2_bundle In oohttp also the same for WINDOW_UPDATE Frame.

sleeyax commented 5 months ago

Can you submit a pr to my fork?

Aron148814 commented 5 months ago

Yea I will do It in couple of days and this Is what I added in the transport.go file.

tls

sleeyax commented 5 months ago

I'll look forward to you PR, I can't comment on a screenshot.

Aron148814 commented 5 months ago

Do you know anything about the Priority flag In the HEADERS Frame? Because I get priority flag on real device (no burp) and It only happens on the site "tls.peet.ws/api/all" not on browserleaks or browserscan. Its not that important because it doesn't change the HTTP/2 Fingerprint but Its still weird. httpheadercompare

sleeyax commented 3 months ago

@Aron148814 have you figured it out by now? I would still be happy to accept a PR for your changes if you can.

Aron148814 commented 3 months ago

@sleeyax Yeah sorry Im kinda been busy this last month but I will try this month for sure.

sleeyax commented 2 months ago

Any news @Aron148814 ?

Aron148814 commented 2 months ago

@sleeyax You didn't saw my pull request on your forked oohttp repository?

sleeyax commented 2 months ago

O.o

No... My bad let me check and review in a moment.

sleeyax commented 2 months ago

Upon reflection, it appears this issue will soon become obsolete. I appreciate your contributions, but in the forthcoming version 2 of Awesome TLS, we will transition away from oohttp. Instead, we will integrate a different library, better suited for customizing network fingerprints specifically and maintained more diligently. Consequently, it is likely that this issue will be resolved automatically upon the release of the next version.