Feature Request – Backup Recovery Passphrase Management #196
Labels
No labels
bug
contribution welcome
duplicate
enhancement
later
not planned
out of scope
question
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
tom79/Holos-App#196
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello,
While backing up the settings of my favorite applications, I wanted to change the recovery passphrase used to restore my Holos settings.
Unfortunately, I was unable to do so. It is possible that I made a mistake when creating the passphrase initially, which now prevents me from using it correctly for restoration purposes.
As far as I can tell, there is currently no way for a user to change or reset this passphrase directly from their own device, even when the device remains accessible and under their control.
I would like to suggest the addition of a secure mechanism that allows users to change or reset their recovery passphrase without compromising the security of their backups.
For example, when a user wishes to update their recovery passphrase, the application could require strong authentication using security methods already available on the device, such as:
Fingerprint authentication;
Facial recognition;
The device PIN, password, or lock-screen credentials.
This approach is widely adopted across modern applications and operating systems. It provides a high level of security while offering a practical and user-friendly way for users to recover from an incorrectly entered passphrase or simply update it when needed.
Such a feature would significantly reduce the risk of permanently losing access to backups due to a typo or forgotten passphrase, while still ensuring that only the legitimate device owner can perform this sensitive operation.
Thank you for your work and for considering this feature request.