[pass] Info

[GOYOT Martin]

Okay, so two answers:

* For Jp, you can find an interactive tutorial at https://try.github.io if
you want to begin with. Please keep in mind that is is actually a
developper tool and some concepts might not be relevant to your needs.

* For Pablo:

The recommended way to deal with login is to use multiline files as shown
here https://www.passwordstore.org/. Point is that in the next release it
will be easy to say to pass which line to copy when you issue a `pass -c`
or `pass show -c` which means that you put the password on the first line
as it is the default and the username on the second line. Then you can
specify which line to copy to either copy user or password. But for now
this feature is not delivered in the current stable version.

I personally do the same thing as you with one folder pro site and a file
with the username because I find it more convenient until the feature
mentioned earlier is delivered. I don't know if this is good or bad
practice but it has worked nicely for me since quite a long time now.

I may be over-interpreting your question, but it seems like you are talking
about pushing your passwords on a github repository or something like this.
My opinion on this is DON'T. Even if you were able to obfuscate the
information about logins and web sites, an attacker can still by "chance"
find your key (this is improbable). Rule #1 is don't provide an attacker
with your files. So, what you have to do is push your git repository on a
private one for instance. Either on your own server, or on a private github
plan, or any other private provider, or you can also directly push from one
device to another (this demands a little bit more of
configuration/understanding).

On Fri, Feb 26, 2016 at 5:21 PM Pablo <binaryplease at gmail.com> wrote:

> Hello,
>
> I too have a question regarding git synchronisation.
> My store has the following structure:
>
> storedir
>    - 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?
> Regards.
>
>
>
> 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
> >
> _______________________________________________
> Password-Store mailing list
> Password-Store at lists.zx2c4.com
> http://lists.zx2c4.com/mailman/listinfo/password-store
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/password-store/attachments/20160226/61efd2a7/attachment.html>