<p dir="ltr">Hello,</p>
<p dir="ltr">Not that I'm aware of. It's the whole business model of github; making things private is not free.</p>
<br><div class="gmail_quote"><div dir="ltr">Jp <<a href="mailto:alcanjp@icloud.com">alcanjp@icloud.com</a>> schrieb am Fr., 4. März 2016 06:52:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    Hi all,<br>
    <br>
      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?<br>
    <br>
    thanks, <br></div><div text="#000000" bgcolor="#FFFFFF">
    <br>
    <div>On 2016-03-03 16:42, GOYOT Martin
      wrote:<br>
    </div>
    </div><div text="#000000" bgcolor="#FFFFFF"><blockquote type="cite">
      <div dir="ltr">Yes, that should do the trick</div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr">On Thu, Mar 3, 2016 at 4:36 PM Harrison Powers
          <<a href="mailto:harrisonpowers@gmail.com" target="_blank">harrisonpowers@gmail.com</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div dir="ltr">
            <div class="gmail_default" style="color:#444444">JP,</div>
            <div class="gmail_default" style="color:#444444">try adding
              trust to the key:</div>
            <div class="gmail_default" style="color:#444444">gpg
              --edit-key KEY_ID</div>
            <div class="gmail_default" style="color:#444444">trust</div>
            <div class="gmail_default" style="color:#444444">5</div>
            <div class="gmail_default" style="color:#444444">save</div>
            <div class="gmail_default" style="color:#444444"><br>
            </div>
            <div class="gmail_default" style="color:#444444">hopefully
              that helps</div>
          </div>
          <div class="gmail_extra"><br>
          </div>
          <div class="gmail_extra">
            <div class="gmail_quote">On Thu, Mar 3, 2016 at 10:24 AM, Jp
              <span dir="ltr"><<a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a>></span>
              wrote:<br>
            </div>
          </div>
          <div class="gmail_extra">
            <div class="gmail_quote">
              <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div text="#000000" bgcolor="#FFFFFF"> 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?<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 the named user<br>
                  gpg: /dev/shm/pass.XXXXXXXXXXXXXXXXXXXX: encryption
                  failed: Unusable public key<br>
                  <br>
                  thanks
                  <div>
                    <div><br>
                      <br>
                      <div>On 2016-02-26 17:11, GOYOT Martin wrote:<br>
                      </div>
                      <blockquote type="cite">
                        <div dir="ltr">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.
                          <div><br>
                          </div>
                          <div>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.</div>
                          <div><br>
                          </div>
                          <div>I would be pleased to answer your
                            questions on the matter if you have any</div>
                        </div>
                        <br>
                        <div class="gmail_quote">
                          <div dir="ltr">On Fri, Feb 26, 2016 at 5:05 PM
                            Jp <<a href="mailto:alcanjp@icloud.com" target="_blank">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">Thank you for
                            the response, well, the idea here is to use
                            Git to<br>
                            propagate the changes between PCs, right?  I
                            guess I was confused<br>
                            because I didn't realize that pass was doing
                            the commit, and it does<br>
                            make sense now.  I just needed to have a
                            clear basic understanding of<br>
                            the process of using pass with Git and since
                            I am not a full blown dev<br>
                            guy, I got confused.  I starting using
                            syncthing that 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 you use it like a<br>
                            > normal git repository by prefixing all
                            your 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 <<a href="mailto:alcanjp@icloud.com" target="_blank"><a href="mailto:alcanjp@icloud.com" target="_blank">alcanjp@icloud.com</a></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 after leaving lastpass.  But<br>
                            >     in terms of being able to sync via
                            Git!  I find the resources very<br>
                            >     confusing and therefor I am looking
                            to get more 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>
                            <mailto:<a href="mailto:Password-Store@lists.zx2c4.com" target="_blank">Password-Store@lists.zx2c4.com</a>><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>
                          </blockquote>
                        </div>
                      </blockquote>
                      <br>
                    </div>
                  </div>
                </div>
                <br>
                _______________________________________________<br>
                Password-Store mailing list<br>
                <a href="mailto:Password-Store@lists.zx2c4.com" target="_blank">Password-Store@lists.zx2c4.com</a><br>
              </blockquote>
            </div>
          </div>
          <div class="gmail_extra">
            <div class="gmail_quote">
              <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><a href="http://lists.zx2c4.com/mailman/listinfo/password-store" rel="noreferrer" target="_blank"><a href="http://lists.zx2c4.com/mailman/listinfo/password-store" target="_blank">http://lists.zx2c4.com/mailman/listinfo/password-store</a></a><br>
                <br>
              </blockquote>
            </div>
            <br>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <br>
  </div></blockquote></div>