Passlock Backup System
Passlock needs a backup system for the security of the credentials. Without backups, Passlock relies solely on a single vault file and its corruption or deletion will cause the user's credentials to be lost forever. That is why Passlock needs a proper backup architecture so that the user can restore their credentials even if the main vault gets damaged. These backups will be automated based on changes and can also be created manually by the user.
1. What this feature offers:
-
Safety from permanent password loss.
-
Less dependence on a single file.
-
Safety from vault corruption and deletion.
-
A better architecture ensuring no loss of credentials.
-
A local-based zero-credential-loss password management system.
2. The first backup will be created as soon as a vault is created using Passlock CLI; this will be labelled as per date and time according to UNIX_EPOCH.
3. The user can manually create backups using the CLI and TUI.
4. The TUI automatically backs up the vault upon exit after changes have been made to the vault.
5. A maximum of 10 backups can be created for a particular vault; after that, the oldest backup will be replaced by the latest backup either automatically or if the user manually creates a backup.
6. Users can restore to a particular backup using the CLI, or they can pass the latest subcommand to restore the latest backup.
With this, I end this issue. Any further notices and updates will be notified in this issue itself.
Passlock Backup System
Passlock needs a backup system for the security of the credentials. Without backups, Passlock relies solely on a single vault file and its corruption or deletion will cause the user's credentials to be lost forever. That is why Passlock needs a proper backup architecture so that the user can restore their credentials even if the main vault gets damaged. These backups will be automated based on changes and can also be created manually by the user.
1. What this feature offers:
Safety from permanent password loss.
Less dependence on a single file.
Safety from vault corruption and deletion.
A better architecture ensuring no loss of credentials.
A local-based zero-credential-loss password management system.
2. The first backup will be created as soon as a vault is created using Passlock CLI; this will be labelled as per date and time according to
UNIX_EPOCH.3. The user can manually create backups using the CLI and TUI.
4. The TUI automatically backs up the vault upon exit after changes have been made to the vault.
5. A maximum of 10 backups can be created for a particular vault; after that, the oldest backup will be replaced by the latest backup either automatically or if the user manually creates a backup.
6. Users can restore to a particular backup using the CLI, or they can pass the
latestsubcommand to restore the latest backup.With this, I end this issue. Any further notices and updates will be notified in this issue itself.