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
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 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
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
I don't entirely agree with all you said, but implementing this as a
user extension sounds like an awesome idea! I'm doing it :D
Any guidelines or whatsoever? How should extensions should be written?
BTW, having a curated list for such extensions is a must have, like
KeePass does.
Cheers!
On