On 29/01/2017 12:18, Emil Lundberg wrote:
If you use gpg-agent, you can instead use `git log -p `,
which shows you the diff for each commit in the log. Git will
automagically decrypt the files before diffing.
"Binary files a/xxx.gpg and b/xxx.gpg differ" - some .gitconfig magic is
required
Hi all,
My personal solution is a (very) small pass extension pass-update [1]
that prints the password and wait for the user before to generate a new
password. It supports xclip interaction and you can change as many
password as you want in the same command:
pass update web/password1
On 28/01/2017 16:42, Simon Lackerbauer wrote:
On 01/28/2017 05:34 PM, Brian Candler wrote:
I like this idea a lot. I like keeping history of passwords, as
sometimes you come across some forgotten system which still uses a
password from one or more generations ago.
Isn't that what's basically
On 01/28/2017 05:34 PM, Brian Candler wrote:
> I like this idea a lot. I like keeping history of passwords, as
> sometimes you come across some forgotten system which still uses a
> password from one or more generations ago.
Isn't that what's basically the point of the git integration? Each
On 28/01/2017 16:21, Patrick Burroughs (Celti) wrote:
I think there's room in this idea for a `pass rotate` subcommand, that
will shove the old password down a line, then generate and insert the
new password. Should be relatively easy to implement*and* would help
satisfy some systems that have
On Sat, 28 Jan 2017 07:40:14 +0100
Lucas Hoffmann wrote:
> Quoting Diego Depaoli (2017-01-27 21:42:11)
> > So to hold it all together, I use a trivial two step solution:
> > first with edit subcommand I manually add an empty line at the top
> > of the file, then with generate
Quoting Diego Depaoli (2017-01-27 21:42:11)
> So to hold it all together, I use a trivial two step solution: first with
> edit subcommand I manually add an empty line at the top of the file, then
> with generate subcommand and --in-place flag i fill it.
> Is there any easier way?
You could try
Il giorno ven 27 gen 2017 alle ore 22:32 ha
scritto:
> > Is there any easier way?
In this case, pass could just echo the old password---that should solve
> this problem, right?
>
Sure, but if you unfortunately run --in-place as first shot... I hope you
have a gited
The --in-place flag is a bit dangerous when you have to enter the old
password before to generate the new one,
The edit subcommand does not automatically generate a new password.
So to hold it all together, I use a trivial two step solution: first with
edit subcommand I manually add an empty line
I haven't used this command personally, but after reading this thread I
found a command that pops open an editor:
pass edit path/to/password
This works for my typical use case.
On Fri, Jan 27, 2017 at 11:09 AM, Emile Cantin
wrote:
> Shouldn't that be the default option?
10 matches
Mail list logo