[pass] [PATCH] Re: Setup for multiple password stores
adam.liter at gmail.com
Tue Feb 16 01:42:22 CET 2016
Thanks everyone for the responses and suggestions.
I think I like the idea of using PASSWORD_STORE_DIR the best if that's
how QtPass works, too, but if I have time, I'll try to test out the
patch and give you some feedback, Lenz.
On 14 Feb 2016, at 12:03, Lenz Weber wrote:
> Well, sorry, this took a while but here it is.
> Feedback is welcome, if there are no more improvements to make this
> could prove useful upstream.
> Am 09.02.2016 um 09:14 schrieb Lenz Weber:
>> I have a patch on the shelf that should make pass behave much better
>> with subrepositories.
>> I'll go search it this evening and send it to you, I would be happy
>> about feedback.
>> On 08.02.2016 19:51, Adam Liter wrote:
>>> I'm wondering what setup folks use for having multiple password
>>> stores, particularly when one of those password stores is shared
>>> between multiple people.
>>> Currently, I'm using a .git directory inside of ~/.password-store
>>> has git submodules.
>>> For example, I currently have the following directory structure:
>>> ├─ .password-store
>>> ├─ personal
>>> └─ collaborative-project
>>> where personal is my personal store of passwords and
>>> collaborative-project contains passwords for a project that I'm
>>> working on with somebody else. Both of these are submodules of the
>>> top-level git directory so that the collaborative-project—but not
>>> personal—repository can be shared with somebody else via git
>>> pushing, and pulling from/to a cloud-hosted git repository.
>>> However, this setup causes the automatic git committing that pass
>>> to break. For example, running:
>>> pass generate personal/asdf 22
>>> fatal: Pathspec
>>> '/Users/adamliter/.password-store/personal/asdf.gpg' is in submodule
>>> The generated password for personal/asdf is:
>>> py?Je17K6Bfs|Pj at qspgE1
>>> So it does generate the password, but the git commits are not
>>> correctly written.
>>> Currently, I'm just manually committing things myself, but I'm
>>> wondering if there is a better setup or workflow to deal with this
>>> sort of situation.
>>> (And thanks, Jason, for an awesome password manager! :) )
>>> Password-Store mailing list
>>> Password-Store at lists.zx2c4.com
>> Password-Store mailing list
>> Password-Store at lists.zx2c4.com
> Password-Store mailing list
> Password-Store at lists.zx2c4.com
More information about the Password-Store