-
Notifications
You must be signed in to change notification settings - Fork 0
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
ios skips pair-verify procedure after pair-setup and goes directly into encrypted communication #2
Comments
It could just be the same keys used for the chacha in pair setup |
Not really sure, tried a few permutations/combinations of HKDF and what not. will monkey patch it for now by forcing ios client to reconnect (and thus use the "proper" pair verify procedure) |
I confirmed that this is the behavior, and ios makes no attempt at pair-verify right after pair-setup (through device logs) |
ok, success! its just the srp shared key! |
Closed by e14eec4 |
This broke just now, for some reason, I do not know why. Right after pairing, |
The data is definitely encrypted, unknown what keys. |
you just need to set the nonce_length to 12 🤦 |
maybe. I'm not really sure though. However, the logs make sense. the question is what keys ios decides to use for chacha!
The text was updated successfully, but these errors were encountered: