> > 2. git adds and commits have to take place in the right repo.
>
This should be easily doable, assuming git>=1.8.2 (if memory serves).
Something like this (completely untested):
git -C "$(dirname \"$passfile\")" add "$passfile"
Since git already does the walking up to the nearest working
On 09/05/2016 16:06, Lukas J wrote:
I would like to change the key I use for encrypting my password. I
couldn't find an option for pass to do that. Is there an easy way to
do it?
Do you mean, re-encrypt all your stored passwords with a different GPG
public key?
I think "pass init " should
I think that "gpg init gpg-id" will do the trick. Check out the manpage:
> If the specified gpg-id is different from the key used in
> any existing files, these files will be reencrypted to use the new id.
On 09/05/16 16:06, Lukas J wrote:
> Hi guys,
>
> I would like to change the key
Hi guys,
I would like to change the key I use for encrypting my password. I
couldn't find an option for pass to do that. Is there an easy way to do it?
Best regards,
Lukas
___
Password-Store mailing list
Password-Store@lists.zx2c4.com
I am using pass under OSX without gpg-agent [^1]
Something I've noticed:
- "pass edit foo/bar" when it creates a new file, doesn't ask for your
passphrase
- "pass edit foo/bar" when editing an existing file asks for your
passphrase both before *and* after editing
I thought this meant that
Quoting Brian Candler (2016-05-09 06:59:43)
> ...
> I have multiple git-backed password stores for different clients. Right
> now I am using wrapper scripts to set the base directory, e.g.
> ...
> 2. git adds and commits have to take place in the right repo.
>
> This will involve either:
> -
(I don't know if this has been discussed or proposed before)
I have multiple git-backed password stores for different clients. Right
now I am using wrapper scripts to set the base directory, e.g.
#!/bin/sh
PASSWORD_STORE_DIR=/Users/brian/git/client1/password-store pass "$@"
#!/bin/sh