0% found this document useful (0 votes)
56 views8 pages

Config Making PART 1

config making part

Uploaded by

mermaid007
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
56 views8 pages

Config Making PART 1

config making part

Uploaded by

mermaid007
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Making your first simple config BY CASSELL

PART 1

The first config is going to be something easy so we are going to start with
[Link]

The debugger we are going to use is fiddler for simplicity


Download link: ​[Link]

First thing you will have to do is go to the site and put in fake info

This is so we dont use out real info.

Now before you hit login we are going to go to fiddler and hit ctrl a than ctrl x to delete than hit
sign in.

You will get something like this


Dont worry if there is more we are just looking for the post in this one
We will want to set it to raw so we can read it

We wont be needing cookies for this but sometimes you do.


POST [Link] HTTP/1.1
Host: [Link]
Connection: keep-alive
Content-Length: 57
Accept: application/json, text/plain, */*
Origin: [Link]
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/73.0.3683.103 Safari/537.36
content-type: text/plain
Referer: [Link]
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9,de;q=0.8

{"username":"​jhgvcuhv@[Link]​","password":"edrtjretdjn"} old post data


{"username":"<USER>","password":"<PASS>"} new post data

We replace the username with <USER> and the password with <PASS> so
“{"username":"​jhgvcuhv@[Link]​","password":"edrtjretdjn"}” will now be
“{"username":"<USER>","password":"<PASS>"}”

Note content type and content length dont need to be in the headers when put into ob
Next we will make our keycheck
To get a keycheck you need to see what your response is so we will his start with a email:pass
in it to see out responce
{"id":"so06-uakr-wwzz","errors":[{"id":"so06-uakr-wwzz","name":"invalidCredentialsError","messa
ge":"Username or password is incorrect."}],"message":"Username or password is incorrect."}

So as we can see this is our response this one clearly tells us the Username or password is
incorrect.
So we will use that as our fail key

Failkey: Username or password is incorrect

Okay now we need to get a success key so best way to do this is to make a account and than
try it

So after making account i get this as a responce


{"user":{"id":"5c1e783b3ad9442b546646af","username":"jbhul","profileImage":{"width":720,"heig
ht":720,"path":"[Link]
23103620165_1548455989336.jpeg","childImages":[{"width":100,"height":100,"path":"[Link]
.[Link]/profile_images/5c1e783b3ad9442b546646af/978723103620165_15484559
89336_100x100.jpeg"},{"width":250,"height":250,"path":"[Link]
ages/5c1e783b3ad9442b546646af/978723103620165_1548455989336_250x250.jpeg"}]}},"nee
ds2FA":false}

So from this we can see that {"user":{"id" is different from the fail source so we can use this as
success key

So
Failkey: Username or password is incorrect
Successkey: {"user":{"id"

All we have to do is input out fail key and success key like so and that is your first config
complete.

You might also like