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.

Sign up for GitHub

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

Jump to bottom

Fix disparity between provisioning with websocket API or REST API #124

Closed
gferon opened this issue Jan 22, 2022 · 0 comments · Fixed by #119
Closed

Fix disparity between provisioning with websocket API or REST API #124

gferon opened this issue Jan 22, 2022 · 0 comments · Fixed by #119

Comments

@gferon
Copy link
Collaborator

gferon commented Jan 22, 2022

Signal Android provisions the account/secondary device entirely using the websocket connection, which doesn't interpret parameters like name or capabilities the same way.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Implement device name encryption and decryption whisperfish/libsignal-service-rs
1 participant
@gferon