-
-
Notifications
You must be signed in to change notification settings - Fork 482
Open
Labels
bugA bug reportA bug report
Description
Version
3.4.1
Source
Google Play
Vault encryption
Yes
Device
Samsung Galaxy S23+
Android version
Android 15
ROM
No response
Steps to reproduce
What a user might intuitively do to separate the unlock and backup password (and which will NOT actually separate the passwords):
- Make sure automatic backups are turned off
- Go to Settings -> Security and Disable “Encryption” under the “Encryption” section
- Restart the app
- Now Enable “Encryption” back
- Put in the backup password
- Turn on “Separate password for backup & export”
- Put in the unlock password
- Create a backup.
- Delete the app.
- Install the app and restore the backup.
The above will cause the bug to occur.
Now this is the workaround I managed to find:
- Make sure automatic backups are turned off
- Go to Settings -> Security and Disable “Encryption” under the “Encryption” section
- Restart the app
- Now Enable “Encryption” back
- Put in the backup password
- Turn on “Separate password for backup & export”
- Put in the backup password (yes, the backup one)
- Tap on “Change password for backup & export”
- Put in the backup password (yes, the backup password again)
- Tap on “Change password” under the “Encryption” section
- Put in the unlock password
- Restart the app
- You can also reinstall the app and restore the encrypted backup using the backup password.
Now the passwords are properly separated. The app can be unlocked using BOTH the backup and unlock password (but I'm not sure that's the intended behavior). Meanwhile, the backup can ONLY be decrypted using the BACKUP password, as it should be.
What do you expect to happen?
I expect the backup and unlock password to be different.
What happens instead?
The unlock password is the only password that can be used to unlock the backup, even though only the backup password should.
Log
No response
Metadata
Metadata
Assignees
Labels
bugA bug reportA bug report