Implement unlocking upon a registration lock (HTTP 423 with PIN-entry)
The Android and iOS apps make cloud-based back-ups these days. If these are enabled, and a user tries to register in Whisperfish, OWS throws a "423 Locked", and we need to supply the PIN that blocks the registration. This is called the "Registration Lock" or "Account Lock" (grep for RegistrationLock in Signal-Android).
Signal-Service tracking issue: https://github.com/Michael-F-Bryan/libsignal-service-rs/issues/54, we first need those APIs upstream.
Currently, a locked account crashes Whisperfish (because of unwrap
on an unknown response code).
Workaround
- Wait 7 days, or;
- Disable the registration lock on the old device in the Settings menu of the Signal app:
- For Android, this seems to be: Settings -> Privacy -> Registration lock,
- and for iOS this is seemingly: Account -> Signal PIN -> Registration lock.
TODO
-
Implement unlocking via the PIN (we might want this soon, possibly even %v0.6.0-beta.1: group management, Group V2 & UUID).
Edited by Ruben De Smet