-
Notifications
You must be signed in to change notification settings - Fork 50
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Create new methods to facilitate adding new import/export formats * Native import/export * Texts
- Loading branch information
Showing
6 changed files
with
224 additions
and
99 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,61 +1,43 @@ | ||
# Vault: rebuild the vault | ||
|
||
If for some reason you wanted to completely rebuild your vault (for example to make bulk changes), here is how to proceed. | ||
If for some reason you wanted to completely rebuild your vault, here is how to proceed. | ||
|
||
## Rebuilding the vault | ||
## Why rebuild the vault? | ||
|
||
Process to rebuild the vault: | ||
Here are some use cases tor rebuild the vault: | ||
|
||
- Export all secrets | ||
- Delete the vault | ||
- Create a new vault and import the secrets | ||
- Rebuilding the vault is the only solution to change the configuration file salt | ||
- Make bulk changes | ||
|
||
## How to proceed | ||
|
||
### Export all secrets | ||
``` | ||
./vault.py --export all.json | ||
# ...type master key | ||
``` | ||
## Rebuilding the vault | ||
|
||
### Write down the list of categories | ||
Process to rebuild the vault: | ||
|
||
Open the vault and take note of all categories and their IDs. | ||
At this time, categories cannot be exported and imported automatically. | ||
- Export the vault to a native file format | ||
- Import the native file to the new vault | ||
|
||
``` | ||
./vault.py | ||
# ...type master key | ||
# ...type 'cat' | ||
# ...write down all categories | ||
``` | ||
## Security notice | ||
|
||
### Delete the vault and configuration file | ||
For obvious reasons, **export files are not encrypted**, all the vault secrets will be stored in clear. | ||
Make sure to safely store the export file and securely dispose of it after its use. | ||
|
||
``` | ||
./vault.py --erase_vault | ||
# ...type 'y' to confirm | ||
``` | ||
## How to proceed | ||
|
||
### Setup a new vault | ||
### Backup the vault and configuration file | ||
|
||
``` | ||
./vault.py | ||
# Choose a new master key and confirm | ||
# and unlock the vault | ||
``` | ||
Importing and exporting is experimental, please backup the vault and configuration file before proceeding. | ||
|
||
### Re-create the categories | ||
### Export the vault | ||
|
||
``` | ||
# ...type 'cat' | ||
# ...re-create the categories (make sure they have the same IDs) | ||
./vault.py --export vault.native --file_format native | ||
# ...type master key | ||
``` | ||
|
||
### Re-import all the secrets | ||
### Import the vault | ||
|
||
``` | ||
./vault.py --import_items all.json | ||
./vault.py --import_items vault.native --file_format native | ||
# ...type master key | ||
# ...review list and type `y` to confirm import | ||
# ...confirm | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.