Skip to content

Commit

Permalink
clarify GPG requirement in README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
thomas-mc-work authored and roddhjav committed Jul 2, 2024
1 parent 064a8ab commit 1980543
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -527,16 +527,15 @@ pass import bitwarden.json -p Import/

## GPG keyring

Before importing data to pass, your password-store repository must exist and your GPG keyring must be usable. In order words you need to ensure that:
Before importing data to pass, your password-store repository must exist and your GPG keyring must be usable. In other words, you need to ensure that:
- All the public gpgids are present in the keyring.
- All the public gpgids are trusted enough.
- All the public gpgids are trusted enough (`ultimate`).
- At least one private key is present in the keyring.

Otherwise, you will get the following error:
`invalid credentials, password encryption/decryption aborted.`

To set the trust on a GPG key, one can run `gpg --edit-key <gpgid>` then `trust`.

To set the trust on a GPG key, one can run `gpg --edit-key <gpgid>`. Next type `trust` and select `5 = I trust ultimately`.

## Security consideration

Expand Down

0 comments on commit 1980543

Please sign in to comment.