Exposing OP of "Exposing Shitty Config Makers SERIES v1"

[71]

Hello, This is my last post for today. If you have sth to tell reply here. I shall give you a reply tomorrow. As I have limitation of 3 comment.


It does matter @ThaAbyssGoD buddy ... take an example of CF. It was easy bypassing before now what? it comes strong. OB was no longer able to bypass it .. the same goes for other PX1, PX2, and PX3. the version updated. It all happens so fast. That xfinity config already uses encrypted headers/request body  i.e "X-hzfdeCEGvt-a" thing .. even though if static string works on April 2021 it would not fucking works on July ... He didn't even modify static string on july ... use your fat head pub. I guess your not a config maker .. just cracker...

The HTTP Send request for xfinity sites can work like this
---You can send on HTTP header like this---
Host:login.xfinity.com
X-hzfdeCEGvt-a:=<RANDOM_STRING>
X-hzfdeCEGvt-b:=<RANDOM_STRING>
X-hzfdeCEGvt-c:=<RANDOM_STRING>
X-hzfdeCEGvt-d:=<RANDOM_STRING>

or

-----You can send on Post body  like this the choice is yours -----
X-hzfdeCEGvt-a:=<RANDOM_STRING>&X-hzfdeCEGvt-a:=<RANDOM_STRING>&X-hzfdeCEGvt-a:=<RANDOM_STRING>&

I have had good experience on those encrypted header.. I can teach you guys how to bypass those headers for 100$.
it works for xfinity,peacockTV,chipotle and some sites.
Doesn't works for: pcoptimum.ca , starbucks .

Contact me if you want
Thanks

[21]

the modification date of the file has nothing to do with the post data /headers OR anything to do with HTTP in general... you keep saying the same shit OVER and OVER and I get what you're saying? You're telling me to use my "fat head" when you're talking shit in a language you can barely speak... sounding cringe as fuck calling someone a "cracker" and calling yourself a "config maker". Its not like you really know anything about HTTP1.0/1.1/2.0/QUIC in general so you just use a tool that does practically everything for you.