[pass] Info

Pablo binaryplease at gmail.com
Fri Feb 26 17:21:10 CET 2016


I too have a question regarding git synchronisation.
My store has the following structure:

   - WebsiteA (folder)
      - user1.gpg (file containing password etc)
      - user2.gpg (file containing password etc)
   - WebsiteB (folder)
      - user1.gpg (file containing password etc)

Meaning, I have folders for the sites and the files are called like the
usernames. I had to do this because I have multiple accounts on some
websites but now I can't push anywhere without letting the world knnow
my usernames.

How can have multiple accounts on websites, no collision betweeen file
names and be able to push without revealing my usernames (Or better:
even don't reveal the sites I have a account on)?

Is there a best practice for this, how do you do it?

On 02/26/2016 05:11 PM, GOYOT Martin wrote:
> Yes you're right the idea is to be able to share those passwords. Just be
> aware that git isn't "propagating". You push to a destination and then your
> other devices have to pull from this destination to be on par with your
> changes.
> I don't know how good or bad you know git, but if the latter, I suggest
> that you look at some git tutorials as in fact pass isn't really doing all
> the work for you you still have to know how it works.
> I would be pleased to answer your questions on the matter if you have any
> On Fri, Feb 26, 2016 at 5:05 PM Jp <alcanjp at icloud.com> wrote:
>> Thank you for the response, well, the idea here is to use Git to
>> propagate the changes between PCs, right?  I guess I was confused
>> because I didn't realize that pass was doing the commit, and it does
>> make sense now.  I just needed to have a clear basic understanding of
>> the process of using pass with Git and since I am not a full blown dev
>> guy, I got confused.  I starting using syncthing that was more straight
>> forward.
>>   Thank you
>> On 26/02/16 16:54, GOYOT Martin wrote:
>>> Hello Jp,
>>> could you please be more specific? The idea is that you use it like a
>>> normal git repository by prefixing all your commands with pass.
>>> Example:
>>> pass git init
>>> pass git remote add origin ssh://some.url
>>> pass git push
>>> and so on...
>>> You don't need to commit, pass will do it for you.
>>> Regards,
>>> Martin
>>> On Fri, Feb 26, 2016 at 4:51 PM Jp <alcanjp at icloud.com
>>> <mailto:alcanjp at icloud.com>> wrote:
>>>     Hello,
>>>       I have been using Pass for a little while after leaving lastpass.
>> But
>>>     in terms of being able to sync via Git!  I find the resources very
>>>     confusing and therefor I am looking to get more info on how to
>> actually
>>>     use GIT.
>>>     Thank you
>>>     _______________________________________________
>>>     Password-Store mailing list
>>>     Password-Store at lists.zx2c4.com <mailto:
>> Password-Store at lists.zx2c4.com>
>>>     http://lists.zx2c4.com/mailman/listinfo/password-store
> _______________________________________________
> Password-Store mailing list
> Password-Store at lists.zx2c4.com
> http://lists.zx2c4.com/mailman/listinfo/password-store

More information about the Password-Store mailing list