Issues with 9gag Token

[theabbie]

The 9gag Token generated by random_sha1() is 40 characters long, and doesn't work now.

On intercepting 9gag token generated by the app, the token is 44 characters long.

It definitely depends on current timestamp as it becomes invalid after some time.

A sample 9gag token is as follows

Y29tLm5pbmVnYWcuYW5kcm9pZC5hcHAqNDFlbmNmYWFp

If we could fix this, that would be really great.

[theabbie]

@and3rson

[theabbie]

UPDATE: The Token is Base64 encoded

on decoding, it gives

com.ninegag.android.app*41encfaai

Thus, the 41encfaai must be related to Timestamp.

[Alexandero89]

Hello @theabbie ,

could you find out how to generate the correct token?
thanks in advance!

[theabbie]

@Alexandero89 no I was unable to find out, and it might not be useful as they could use some encryption or periodically change the format, it won't be worth finding out.

[Alexandero89]

@theabbie
Thanks for your quick response!

Actually i think its not really easy for them to quickly change this part.
I mean, there are thousands/millions of clients using this format and they would break 95% of all clients if they change it.
because they cant force everyone to update their client.

anyway i maybe found a working solution.
The important part where the timestamp is combined with the token can be found here
will test it tomorrow.