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

Linking secondary devices #3173

Open
madduck opened this issue Oct 25, 2022 · 1 comment
Open

Linking secondary devices #3173

madduck opened this issue Oct 25, 2022 · 1 comment
Assignees

Comments

@madduck
Copy link

madduck commented Oct 25, 2022

The proprietary WhatsApp client can authenticate other clients, such as WhatsApp Web. To link such a secondary device, a QR code generated on the secondary device is scanned by the primary client. Presumably, this is a public key, signed by the primary client, then uploaded to the WhatsApp servers, thus giving the secondary client access to the account. I don't know the details of this (yet), but it's probably the same as what Signal is doing.

If yowsup were able to sign keys like this, i.e. I scan the QR code, obtain the key in plain text, feed it to yowsup, which then uploads the signed key to the WA servers, I could write a yowsup dummy client that just stays online — thus fulfilling the requirement not to be offline for more than 14 days, else your linked devices get unlinked — dropping all content, and I could use a secondary device (e.g. a Matrix bridge) for all my WhatsApp needs.

Is this something worth considering?

Repository owner deleted a comment from Macarthurval Nov 29, 2022
Repository owner deleted a comment from antonio199205 Nov 29, 2022
@tgalal
Copy link
Owner

tgalal commented Nov 29, 2022

It is something indeed worth considering, although unfortunately no time from my side to implement it for the time being.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants