Skip to content
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

Closed
p2p-sys opened this issue Dec 16, 2023 · 7 comments
Closed

DevPwd_InvalidSalt #2

p2p-sys opened this issue Dec 16, 2023 · 7 comments
Labels

Comments

@p2p-sys
Copy link

p2p-sys commented Dec 16, 2023

It is possible to update the protocol. On firmware 2023 this error

python3 main.py 89B0A4EAAABBBCC

:55246 <<< www.easy4ipcloud.com:8800
HTTP/1.1 403 Forbidden
CSeq: 5
Content-Type:
Content-Length: 95

4DevPwd_InvalidSaltp2p,udprelay Error: Forbidden
@khoanguyen-3fc
Copy link
Owner

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.

@khoanguyen-3fc
Copy link
Owner

Positive update, I was able to capture the packets using the newer client!

However, addressing this seems like a bit of a rabbit hole, and unfortunately, I can only dedicate my free time to it, which might extend over the course of weeks or months.

@khoanguyen-3fc
Copy link
Owner

Quick update, I was able to reproduce the DevAuth field, it use HMAC with SHA256 hash.

But I'm also trying to figure out the encryption method for the LocalAddr field, it seems to involve some kind of KDF + AES.

@p2p-sys side question, how was you able to find the password for the cba1b29e32cb17aa46b8ff9e73c7f40b user?

@khoanguyen-3fc
Copy link
Owner

You can take a look at my latest commit (db283e9) for the Python implementation. Feel free to test it with the -t 1 argument.

However, I'm still unable to get it to pass the PTCP handshake with the device. Do you have any ideas?

@khoanguyen-3fc
Copy link
Owner

Thanks to your help, I've been able to properly handle the STUN protocol.

Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Jan 28, 2024
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants