Hello, Not that I'm aware of. It's the whole business model of github; making things private is not free.
Jp <[email protected]> schrieb am Fr., 4. März 2016 06:52: > Hi all, > > I am coming back on the Git subject and is there a way to keep the *.gpg > private on github without having to pay for it or another service? > > thanks, > > On 2016-03-03 16:42, GOYOT Martin wrote: > > Yes, that should do the trick > > On Thu, Mar 3, 2016 at 4:36 PM Harrison Powers <[email protected]> > wrote: > >> JP, >> try adding trust to the key: >> gpg --edit-key KEY_ID >> trust >> 5 >> save >> >> hopefully that helps >> >> On Thu, Mar 3, 2016 at 10:24 AM, Jp <[email protected]> wrote: >> >>> I migrated to a Linux box and when I edit a store it gives me this. On >>> my MAC OS there is no issue other than my Mac uses VI and this box uses >>> Nano, could that be it? >>> >>> And it is the same key! >>> >>> GPG encryption failed. Retrying. >>> gpg: XXXXXXXX: There is no assurance this key belongs to the named user >>> gpg: /dev/shm/pass.XXXXXXXXXXXXXXXXXXXX: encryption failed: Unusable >>> public key >>> >>> thanks >>> >>> >>> On 2016-02-26 17:11, 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 <[email protected]> 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 <[email protected] >>>> > <mailto:[email protected]>> 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 >>>> > [email protected] <mailto: >>>> [email protected]> >>>> > http://lists.zx2c4.com/mailman/listinfo/password-store >>>> > >>>> >>> >>> >>> _______________________________________________ >>> Password-Store mailing list >>> [email protected] >>> >> http://lists.zx2c4.com/mailman/listinfo/password-store >>> >>> >> >
_______________________________________________ Password-Store mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/password-store
