| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Get rid of push/pull shortcuts, as they weren't widely used.
Add contents to repo on git init.
Centralize git add logic, and make it less error prone.
|
|
|
|
Import passwords as multiline entries with password in the first
line. Rest contains following data if they exist in the entry element
of the xml file:
- username
- url
- comment
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Laurent asked for this.
Reported-by: Laurent Ghigonis <laurent@p1sec.com>
|
|
Reported-by: Laurent Ghigonis <laurent@p1sec.com>
|
|
|
|
|
|
|
|
|
|
This should be removed at somepoint in the future. Currently, the
Homebrew people need something to make them happy. This is it.
|
|
|
|
|
|
|
|
Reported-by: Brian Mattern <rephorm@rephorm.com>
|
|
Right now, every time I call pass to decrypt a key, I get output like:
You need a passphrase to unlock the secret key for
user: "User Name <user@domain.com>"
2048-bit ELG-E key, ID XXXXXXNX, created 2012-04-20 (main key ID NNXXNNNX)
password
This patch cleans it up so that only the password is output. I use
pinentry-gtk-2 to enter the gpg passphrase, so this information is
redundant to me. I haven't tried other pinentry versions to see if they
repeat the information as well.
|
|
|
|
this allows the full entry to be completed with a single tab if there is
only one entry in a folder
e.g., given:
amazon.com
user at domain.com
google.com
user1
user2
`pass am<tab>` -> `pass amazon.com/user at domain.com`
while
`pass goo<tab>` -> `pass google.com/`
(previously, the amazon completion would have stopped at amazon.com
despite only a single entry existing)
|
|
Currently, if you hit ctrl-c at the standard 'Enter password' prompt,
since it is piped directly to gpg, the entry gets cleared. Trying to
read from that entry results in:
gpg: [don't know]: 1st length byte missing
This patch fixes this.
Tweaked by Jason A. Donenfeld <Jason@zx2c4.com> to add GNU readline
features by using -e in read.
|
|
This asks before inserting a password when one already exists at that
location (instead of just overwriting it).
|
|
|
|
|
|
|
|
I like being able to specify command line options (like -c) at the end
of the line (which is usually when I think of the fact that I need
them).
The attached patch uses getopt(1) to regularize the option list so that
lazy people like me can specify the options in any order.
|
|
Attached is a trivial patch that removes the quotes from the line that
invokes $EDITOR. It's perfectly cromulent to set $EDITOR to something
with spaces in it, so when we evaluate this one we want it evaluated
bare. For example security nerds might want EDITOR='vim -n' if they
are scared of swap files, and that breaks if we quote there.
|
|
A user made this request:
I was wondering whether it is in a planning to have multiple
password-store directory trees or possible to achieve? eg.
$HOME/.pwd-store-work and $HOME/.pwd-store-home. Maybe distinguish them
with a command line switch and then create aliases in .bash_aliases?
Why I'm asking is that I have multiple major password categories -
personal, work etc. It'll be nice to keep them separate and under
different repos.
Reported-by: Simon KP <si@eskp.net>
|
|
Only GNU systems have --tmpdir, so for other systems we use the TMPDIR
environment variable.
Reported-by: Alexis <surryhill@gmail.com>
|
|
|
|
|
|
|
|
This allows users to edit password files using temporary files created
in /dev/shm. This commit also tidies other things up and fixes minor
bugs and griviences that should be separate commits but aren't.
Reported-by: rupa <rupa@lrrr.us>
|
|
this allows completing password entries without explicitly typing 'show'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The default permissions set by 'install' are 0755 which is not
what we want for manpages and the bash completion file.
|
|
It's meant to be source, so no need for it to start with #!/bin/bash
rpmlint complains about this.
|