kpitt/gopass

An experimental fork of gopass, the "slightly more awesome standard unix password manager for teams"

gopass's Issues

The `init` command doesn't fail immediately if store is already initialized

Summary

When running init on an already-initialized store, it immediately reports that the store is already initialized, but the command doesn't fail until after the user selects the GPG key to use.

Steps To Reproduce

1. Initialize the root password store with gopass init
2. Run gopass init a second time

Expected behavior

The command should detect an already-initialized store and fail immediately. It should not prompt the user for additional information that will never be used.

Additional context

The second gopass init command produces the following output:

Initializing a new password store:

✗ Store is already initialized!
- Searching for usable private keys...
! Hint: Use 'gopass init <subkey> to use subkeys!'
? Please select a private key for encrypting secrets:
[...]
Please enter the number of a key (0-2, [q]uit) (q to abort) [0]: 2

Error: Failed to initialize store: failed to init store "" at "~/.local/share/gopass/stores/root": failed to initialize new sub store: found already initialized store at "~/.local/share/gopass/stores/root".
You can add secondary stores with 'gopass init --path <path to secondary store> --store <mount name>'
`

`init` doesn't recognize an initialized store if using a different crypto provider

Summary

If you run the init command after a password store has already been initialized, but specify a different crypto provider than the one used in the initialized store, init will not recognize that the store is already initialized.

Steps To Reproduce

1. Make sure that the root password store is not initialized (e.g. set GOPASS_HOMEDIR to a new temp directory)
2. Run gopass init to initialize the root store with the default GPG encryption.
3. Run gopass init --crypto age to initialize the root store with Age encryption.

Expected behavior

When running the second gopass init command, it should report that the store is already initialized. If you run gopass init twice with the same crypto provider, it will report:

✗ Store is already initialized!