req_token for 9.40.6.0

[barns]

It seems as though Snapchat have added some complexity to the way that the req_token is generated. Has anyone worked out how to generate the additional parts of the token?

The first part is still a hash of the auth token along with the same secret, merged with a hash of the secret and the timestamp, as seen in this repo eg:

8dbba1d6f9c85089ae8720cab808f9d440a3fd744e80b9af31c3b4e2b6a8f5f0

Then, there is a 34 character string, presumably an MD5 hash, which appears to be dependant on the username, and possibly the date - this part of the token appears to change from day-to-day, but not with different timestamps, eg:

P1e1c2b43d77494114b60b43af5cd69a13

Lastly, there is another 64 character string, probably another sha256 hash, which changes based on timestamp/username, eg:

fa88fb8e2080d6932202f011150711d6abc6ec5c7b10ba9b01248f547023da3e

Has anyone got an algorithm capable of generating the second and third parts of the token?

Cheers

[sandor111]

It seems as though Snapchat have added some complexity to the way that the req_token is generated. Has anyone worked out how to generate the additional parts of the token?

The first part is still a hash of the auth token along with the same secret, merged with a hash of the secret and the timestamp, as seen in this repo eg:

8dbba1d6f9c85089ae8720cab808f9d440a3fd744e80b9af31c3b4e2b6a8f5f0

Then, there is a 34 character string, presumably an MD5 hash, which appears to be dependant on the username, and possibly the date - this part of the token appears to change from day-to-day, but not with different timestamps, eg:

P1e1c2b43d77494114b60b43af5cd69a13

Lastly, there is another 64 character string, probably another sha256 hash, which changes based on timestamp/username, eg:

fa88fb8e2080d6932202f011150711d6abc6ec5c7b10ba9b01248f547023da3e

Has anyone got an algorithm capable of generating the second and third parts of the token?

Cheers

Hi did you find the solution for this?