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

ios skips pair-verify procedure after pair-setup and goes directly into encrypted communication #2

Closed
thiccaxe opened this issue Feb 18, 2024 · 8 comments
Assignees
Labels
investigate An issue needs more research

Comments

@thiccaxe
Copy link
Owner

maybe. I'm not really sure though. However, the logs make sense. the question is what keys ios decides to use for chacha!

@thiccaxe thiccaxe added the investigate An issue needs more research label Feb 18, 2024
@thiccaxe thiccaxe self-assigned this Feb 18, 2024
@thiccaxe
Copy link
Owner Author

It could just be the same keys used for the chacha in pair setup

@thiccaxe
Copy link
Owner Author

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)

@thiccaxe
Copy link
Owner Author

I confirmed that this is the behavior, and ios makes no attempt at pair-verify right after pair-setup (through device logs)

@thiccaxe
Copy link
Owner Author

ok, success! its just the srp shared key!

@thiccaxe
Copy link
Owner Author

Closed by e14eec4

@thiccaxe
Copy link
Owner Author

This broke just now, for some reason, I do not know why.

Right after pairing, _systemInfo is sent, and decrypted properly. Then there are some issues with the next packet. Investigating.

@thiccaxe
Copy link
Owner Author

The data is definitely encrypted, unknown what keys.

@thiccaxe
Copy link
Owner Author

you just need to set the nonce_length to 12 🤦

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigate An issue needs more research
Projects
None yet
Development

No branches or pull requests

1 participant