<div dir="ltr">Maybe bitbucket provides free private repositories I don't know.</div><br><div class="gmail_quote"><div dir="ltr">On Fri, Mar 4, 2016 at 9:46 AM Jp <<a href="mailto:alcanjp@icloud.com">alcanjp@icloud.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I thought so!<br>
<br>
On 04/03/16 09:02, GOYOT Martin wrote:<br>
> Hello,<br>
><br>
> Not that I'm aware of. It's the whole business model of github; making<br>
> things private is not free.<br>
><br>
><br>
> Jp <<a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a> <mailto:<a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a>>> schrieb am Fr., 4.<br>
> März 2016 06:52:<br>
><br>
>     Hi all,<br>
><br>
>       I am coming back on the Git subject and is there a way to keep the<br>
>     *.gpg private on github without having to pay for it or another service?<br>
><br>
>     thanks,<br>
><br>
>     On 2016-03-03 16:42, GOYOT Martin wrote:<br>
>>     Yes, that should do the trick<br>
>><br>
>>     On Thu, Mar 3, 2016 at 4:36 PM Harrison Powers<br>
>>     <<a href="mailto:harrisonpowers@gmail.com" target="_blank">harrisonpowers@gmail.com</a> <mailto:<a href="mailto:harrisonpowers@gmail.com" target="_blank">harrisonpowers@gmail.com</a>>> wrote:<br>
>><br>
>>         JP,<br>
>>         try adding trust to the key:<br>
>>         gpg --edit-key KEY_ID<br>
>>         trust<br>
>>         5<br>
>>         save<br>
>><br>
>>         hopefully that helps<br>
>><br>
>>         On Thu, Mar 3, 2016 at 10:24 AM, Jp <<a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a><br>
>>         <mailto:<a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a>>> wrote:<br>
>><br>
>>             I migrated to a Linux box and when I edit a store it gives<br>
>>             me this.  On my MAC OS there is no issue other than my Mac<br>
>>             uses VI and this box uses Nano, could that be it?<br>
>><br>
>>             And it is the same key!<br>
>><br>
>>               GPG encryption failed. Retrying.<br>
>>             gpg: XXXXXXXX: There is no assurance this key belongs to<br>
>>             the named user<br>
>>             gpg: /dev/shm/pass.XXXXXXXXXXXXXXXXXXXX: encryption<br>
>>             failed: Unusable public key<br>
>><br>
>>             thanks<br>
>><br>
>><br>
>>             On 2016-02-26 17:11, GOYOT Martin wrote:<br>
>>>             Yes you're right the idea is to be able to share those<br>
>>>             passwords. Just be aware that git isn't "propagating".<br>
>>>             You push to a destination and then your other devices<br>
>>>             have to pull from this destination to be on par with your<br>
>>>             changes.<br>
>>><br>
>>>             I don't know how good or bad you know git, but if the<br>
>>>             latter, I suggest that you look at some git tutorials as<br>
>>>             in fact pass isn't really doing all the work for you you<br>
>>>             still have to know how it works.<br>
>>><br>
>>>             I would be pleased to answer your questions on the matter<br>
>>>             if you have any<br>
>>><br>
>>>             On Fri, Feb 26, 2016 at 5:05 PM Jp <<a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a><br>
>>>             <mailto:<a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a>>> wrote:<br>
>>><br>
>>>                 Thank you for the response, well, the idea here is to<br>
>>>                 use Git to<br>
>>>                 propagate the changes between PCs, right?  I guess I<br>
>>>                 was confused<br>
>>>                 because I didn't realize that pass was doing the<br>
>>>                 commit, and it does<br>
>>>                 make sense now.  I just needed to have a clear basic<br>
>>>                 understanding of<br>
>>>                 the process of using pass with Git and since I am not<br>
>>>                 a full blown dev<br>
>>>                 guy, I got confused.  I starting using syncthing that<br>
>>>                 was more straight<br>
>>>                 forward.<br>
>>><br>
>>>                   Thank you<br>
>>><br>
>>>                 On 26/02/16 16:54, GOYOT Martin wrote:<br>
>>>                 > Hello Jp,<br>
>>>                 ><br>
>>>                 > could you please be more specific? The idea is that<br>
>>>                 you use it like a<br>
>>>                 > normal git repository by prefixing all your<br>
>>>                 commands with pass.<br>
>>>                 ><br>
>>>                 > Example:<br>
>>>                 ><br>
>>>                 > pass git init<br>
>>>                 > pass git remote add origin ssh://some.url<br>
>>>                 > pass git push<br>
>>>                 ><br>
>>>                 > and so on...<br>
>>>                 ><br>
>>>                 > You don't need to commit, pass will do it for you.<br>
>>>                 ><br>
>>>                 > Regards,<br>
>>>                 > Martin<br>
>>>                 ><br>
>>>                 > On Fri, Feb 26, 2016 at 4:51 PM Jp<br>
>>>                 <<mailto:<a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a>><a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a><br>
>>>                 <mailto:<a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a>><br>
>>>                 > <mailto:<a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a><br>
>>>                 <mailto:<a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a>>>> wrote:<br>
>>>                 ><br>
>>>                 >     Hello,<br>
>>>                 ><br>
>>>                 >       I have been using Pass for a little while<br>
>>>                 after leaving lastpass.  But<br>
>>>                 >     in terms of being able to sync via Git!  I find<br>
>>>                 the resources very<br>
>>>                 >     confusing and therefor I am looking to get more<br>
>>>                 info on how to actually<br>
>>>                 >     use GIT.<br>
>>>                 ><br>
>>>                 ><br>
>>>                 >     Thank you<br>
>>>                 >     _______________________________________________<br>
>>>                 >     Password-Store mailing list<br>
>>>                 >     <a href="mailto:Password-Store@lists.zx2c4.com" target="_blank">Password-Store@lists.zx2c4.com</a><br>
>>>                 <mailto:<a href="mailto:Password-Store@lists.zx2c4.com" target="_blank">Password-Store@lists.zx2c4.com</a>><br>
>>>                 <mailto:<a href="mailto:Password-Store@lists.zx2c4.com" target="_blank">Password-Store@lists.zx2c4.com</a><br>
>>>                 <mailto:<a href="mailto:Password-Store@lists.zx2c4.com" target="_blank">Password-Store@lists.zx2c4.com</a>>><br>
>>>                 ><br>
>>>                  <a href="http://lists.zx2c4.com/mailman/listinfo/password-store" rel="noreferrer" target="_blank">http://lists.zx2c4.com/mailman/listinfo/password-store</a><br>
>>>                 ><br>
>>><br>
>><br>
>><br>
>>             _______________________________________________<br>
>>             Password-Store mailing list<br>
>>             <a href="mailto:Password-Store@lists.zx2c4.com" target="_blank">Password-Store@lists.zx2c4.com</a><br>
>>             <mailto:<a href="mailto:Password-Store@lists.zx2c4.com" target="_blank">Password-Store@lists.zx2c4.com</a>><br>
>><br>
>>             <<a href="http://lists.zx2c4.com/mailman/listinfo/password-store" rel="noreferrer" target="_blank">http://lists.zx2c4.com/mailman/listinfo/password-store</a>><a href="http://lists.zx2c4.com/mailman/listinfo/password-store" rel="noreferrer" target="_blank">http://lists.zx2c4.com/mailman/listinfo/password-store</a><br>
>><br>
>><br>
><br>
</blockquote></div>