WhatsApp to release password reminder feature for end-to-end encrypted backups
and on Freeview 262 or Freely 565
WhatsApp is set to begin rolling out a new feature that will allow users to verify if the password on their end-to-end encrypted backups is correct. It will then allow users to replace the password if there is an incorrect match.
The new feature has already been made available to some users by installing the latest version of the instant messaging app for both iOS and Android. WhatsApp announced end-to-end encryption backups in a blog post two years ago and has since made updates to the feature.
Advertisement
Hide AdAdvertisement
Hide AdUsers can secure their backups using end-to-end encryption by either choosing a personal password or a 64-digit encryption key. Only the user will know this information, with neither WhatsApp or the back-up service providers, which includes Apple and Google, being able to read encrypted backups or unlock them.
WhatsApp had previously used its own encryption techniques to protect backups in the past, but this was not end-to-end encryption. The update has caused some users however to lose access to their encrypted backups after forgetting their passwords.
WhatsApp’s new feature will allow users to verify the password after installing the latest version of the instant messaging app, which could potentially allow users back into their backups. When loading up WhatsApp users may be prompted to enter their passwords that were chosen to encrypt their backups on Google Drive and iCloud.
The new feature is a reminder so that users can confirm whether the password is correct. The pop-up will automatically appear at random, with no current way to force the prompt to appear.
If you don’t remember your password, then you can reset your backups by disabling end-to-end encrypted backups and then reactivating the feature with a new password.
Comment Guidelines
National World encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.