-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adaptable to honor 3 router ? #7
Comments
Hello, If you can still access the router when it crashes and you are able to reboot it using web interface, you can try checking what is being sent from the browser (simplest way is to open Chrome or Firefox Developer tools) and see if it is similar to what this script is doing. |
Hi i think he meant the Huawei AX3 router.. i have the same and have been testing it.. it seems it generates on the get cmd index/html it displays 2 csrf tokens 1 - csrf_param 2 csrf_token this 2 are used on the next post cmd sending /user_login_nonce with the following payload {"data":{"username":"admin","firstnonce":"39615b801978ee026daef7e00bbe93b89823f1e2226bcf3405377e0ec6b28973"},"csrf":{"csrf_param":"BIux9dmPgXOjvIHr5BeONJx8OBnASv57","csrf_token":"jxqEchfqKEzadcC6WG0uMeJNJlJ8KEfR"}} after we input the password, becuase the router username is embedded on the firmware as admin only.. and the firstnonce is generated on the server router side.. i have readn on chinese csdn site that its a random generator using SCRAM.. but so far i cannot get past this step.. on my python script also.. and it replies a errorcode 1... but on the original debug log it posts back itineration, exponente 10001 and RSA_N and some other keys finalnonce, which will be then after used on the next POST cmd /usr_login_proof this cmd sends back the password encrypted using the following algo which i have managed to exctract from script.js inside the router |
Hi guys,
I do have a honor 3 router which keeps crashing. And I would love to get that script working on that device.
Can anyone let me know i there is a chance to get this running ?
Thanks !
The text was updated successfully, but these errors were encountered: