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
DevPwd_InvalidSalt #2
Comments
I've noticed that newer clients include device credentials when creating a P2P channel. However, to simplify the process and prioritize user privacy (since other users won't need to include device credentials when reporting issues), I've chosen to stick with the older protocol. Could you provide additional details? This includes the device model, a pcap dump, and/or a link to download a Windows client compatible with your device. If possible, an official link like this one would be ideal. I'll do my best to avoid requesting your device credentials. However, it's challenging to guarantee the code's compatibility since my device doesn't require them. If you're open to it, would you consider implementing it directly? I'd be more than happy to merge it. |
Quick update, I was able to reproduce the But I'm also trying to figure out the encryption method for the @p2p-sys side question, how was you able to find the password for the |
You can take a look at my latest commit (db283e9) for the Python implementation. Feel free to test it with the However, I'm still unable to get it to pass the PTCP handshake with the device. Do you have any ideas? |
Thanks to your help, I've been able to properly handle the STUN protocol. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
It is possible to update the protocol. On firmware 2023 this error
python3 main.py 89B0A4EAAABBBCC
4DevPwd_InvalidSaltp2p,udprelay Error: ForbiddenThe text was updated successfully, but these errors were encountered: