-
Notifications
You must be signed in to change notification settings - Fork 11
parse_token returns wrong ajax token #85
Comments
@hiikion, Thank you very much! Fix: execute |
#86 I tested the fix works |
I've checked token parser using |
Oh, that's because of |
I think the most efficient solution is to create the accurate copy of |
Temporarily fixed |
That happened again: Aternos added |
|
Is the cause known? |
@pythoncat1, yes. Please, read the conversation above. |
So I imagine #85 (comment) must be done? |
may be related to #75 (comment)
(i dont think ajax tokens are sensitive info but will censor them anyway)
I noticed in the dev console that the ajax token used by aternos did not match the one given by the library
LGuu****************
< used by aternos websiteTBsn****************
< used by the libraryI deobfuscated the js function by hand to try and understand how it works
And yeah it just sets the
AJAX_TOKEN
toLGuu****************
its all determined by the!
i tested and the
to_ecma5
dosent seem to be the thing causing the error.If a had to guess its probably the
ctx.execute('window.document = { };')
and the others that are causing the problem.The text was updated successfully, but these errors were encountered: