#1
OP 31 July, 2020 - 02:14 PM
Something that interests me so fucking much is how some sites and security measures actually fingerprint certain checkers. Openbullet is a very powerful tool but recently it's power has been limited MAJORLY. A new authorization header/measure called "Sensor Data" has popped into the scene and (prove me wrong) is 99% Impossible to bypass in openbullet. From what I've read upon sensor data actually works INTERNALLY as a majority. Reading hardware and MAC-ID's. one factor is the way the Sensor data actually traces mouse movements and browser lengths (simialar to Akamai) etc. Say for example if there is no 1.1m of mouse movement in total from the login page then upon requesting a login you will be unable to connect to api. Other things have very well surprised me in which Minecraft configs are fairly impossible in Openbullet due to how Mojang detects its Websockets and processes it. It's also why you'll see NETFLIX checkers and SNIPR configs but you'll RARELY find one in openbullet. 

One thing I would say is that I'd recommend switching up tools every once in a while and get into pentesting through c# where websockets and sensor data can actually be manipulated. Not saying c# is the only language but it seems as if Openbullet is becoming dry an outdated.

Also if I'm wrong with any of these please correct me. This shit is beyond interesting to me  Pepelove
 
[Image: bXABN2d.gif] CLICK ME 
[Image: tGHNWQR.png]
[Image: Z8rHRHx.png]