Set up another PC to access pass's remote git repository

Ethan Beyak ethanbeyak at
Mon Oct 16 07:15:58 CEST 2017

Thanks all for the discussion. I do realize the privacy issue, storing the
password names in a public repository, but as with Mark above, that's all I
could figure out in the beginning.

Thanks for letting me know Alec that Gitlab and BitBucket have free private
repos -- I'll migrate this week.

And thank you Niels for the information on exporting / importing my
gpg-key-pair. First time doing it -- I'll try not to royally screw up like
the recent incident from Adobe's Product Security Team...

On Sun, Oct 15, 2017 at 11:52 PM, Alec Clews <alecclews at> wrote:

> On 16/10/17 15:35, Niels Kobschaetzki wrote:
>> The only problem I see might be privacy implications since other people
>> can publicly see what for sites he is using, if he names his passwords
>> accordingly. Maybe the user should invest in a github subscription to be
>> able to create a private repository.
> That was my concern -- I want to hide as much information as possible.
> You can get free private repos on Gitlab or BitBucket.....
> --
> Alec Clews
> Personal <alec.clews at>             Melbourne, Australia.
> Jabber:  alecclews at             PGPKey ID: 0x9BBBFC7C
> blog:
> _______________________________________________
> Password-Store mailing list
> Password-Store at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Password-Store mailing list