You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
perhaps it it's obvious to most people or i am the first who ran into this due to having too many VMs and RPIs on the desk, but for the chance of helping others stubborn like me:
the webbrowser for obtaining the stok (URL token) and the python script running the exploit have to use the same source IP for the DUT.
(off course you might use a squid proxy, a nginx as reverse, some nat-rule or any other method to have the same effect.)
i realized this fault (which cost me several hourse to find) by uncomming the to print-statements
#print (r1.text)
#print (r2.text)
which then gave me the error reply (afaik) "illegal token".
i would suggest to add this to the doc (or even on the input dialoge)
The text was updated successfully, but these errors were encountered:
perhaps it it's obvious to most people or i am the first who ran into this due to having too many VMs and RPIs on the desk, but for the chance of helping others stubborn like me:
the webbrowser for obtaining the stok (URL token) and the python script running the exploit have to use the same source IP for the DUT.
(off course you might use a squid proxy, a nginx as reverse, some nat-rule or any other method to have the same effect.)
i realized this fault (which cost me several hourse to find) by uncomming the to print-statements
#print (r1.text)
#print (r2.text)
which then gave me the error reply (afaik) "illegal token".
i would suggest to add this to the doc (or even on the input dialoge)
The text was updated successfully, but these errors were encountered: