How many of them are unique?
Every unique item in a week/month time could be considered an install and
will try another way to install it (via https). All the other ones are
basically syncing. You could whitelist them for plain git and blacklist
everything else. Then after some more months try to
Jason A. Donenfeld:
> Welp, in the last 2 days:
>
> krantz log # grep git-daemon messages | grep 'Connection from' | wc -l
> 3079
>
> So, I guess git:// will be sticking around, alas.
That just means ppl haven't changed their remotes.
if you choose an ultimatum date, like say in 3 months, and
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
Hello Patrick,
I'm pretty sure you haven't done anything wrong. I'm also an OSX user and a
Linux user and I use a pass store initialized on a Linux and the behaviour
is the same.
So maybe the documentation is out of date or something has been
broken/changed in the code, but I would say that this
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
Yep "propagating" is the wrong term for this! I am essentially clueless
when it comes to Git. I do understand the concept of being a
collaboration tool. I did go on YouTube to get the bases of the tool, I
just need to play with it and I didn't want to accidentally delete my
password in the
Hi,
I have just installed password-store on the advice of lots of friends! -
loving it. I am currently using it on osx, and I was creating some test
files and running pass.
The output of pass gives me:
Password Store
├── something.gpg
└── test.gpg
Which is very slightly different from what is
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
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
___
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.
Welp, in the last 2 days:
krantz log # grep git-daemon messages | grep 'Connection from' | wc -l
3079
So, I guess git:// will be sticking around, alas.
___
Password-Store mailing list
Password-Store@lists.zx2c4.com
11 matches
Mail list logo
