Attached.
Von
keepassx2pass-fixes.patch
Description: Binary data
___
Password-Store mailing list
Password-Store@lists.zx2c4.com
http://lists.zx2c4.com/listinfo.cgi/password-store-zx2c4.com
I believe attachment on my last email got scrubbed, including inline this time.
Von
>From d500238fbbd421b69d53a03546a1b93641211ce9 Mon Sep 17 00:00:00 2001
From: Von Welch
Date: Mon, 11 Feb 2013 21:08:25 -0500
Subject: [PATCH 1/2] keepassx2pass.py: Handle empty password.
---
cont
Fix for my previous patch for keepassx2pass.py, carriage return should
have been '\n' not '\N'
Von
---
contrib/keepassx2pass.py |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/contrib/keepassx2pass.py b/contrib/keepassx2pass.py
index 6cf2268..1804e33 100755
--- a/contri
Hello,
I'm running pass inside of tmux on MacOSX. In order to access the
paste buffer, I need to wrap the calls to pbcopy/pbpaste (xclip
replacement) with reattach-to-user-namespace as described at:
http://robots.thoughtbot.com/post/19398560514/how-to-copy-and-paste-with-tmux-on-mac-os-x
Whats
As a user, I would just like to say this would be a useful addition. One of
the first things I did to use pass was write a function to do this sort of
searching.
Von
On Wed, Apr 3, 2013 at 3:15 PM, Alexis wrote:
> Hi all,
> please find attached my proposed patch that adds the find/search
> comm
But the move is right before the "if " clause.. when not make that
clause into a "if mv else git mv"?
Having this be a git mv when appropriate would make the git log more clear.
Von
On Mon, Apr 15, 2013 at 4:44 PM, Brian Mattern wrote:
> To answer my own question, you've already moved the fi
Attached is a fix for a bug introduced
in c832d4647439a0d504a310fba51f20dcb5051c47 in that the 'mkdir -p' for
pass.bash-completion no longer matches the path for the installation.
Von
http://git.zx2c4.com/password-store/commit/Makefile?id=c832d4647439a0d504a310fba51f20dcb5051c47
0001-Makefile-a
The attached patch adds a new option to 'show' which is '-t/--tail' which
causes pass to print the 2nd and subsequent lines of a password file.
You can use it with '-c/--clip' to put the first line to the clipboard and
the 2nd and subsequent lines to stdout, or use it alone to just print the
2nd a
Hi,
I'm said author of the -tail. I'll just add one thing about --tail to what
Jonas and Philip have said and that it works intelligently with -c, so '-t'
along doesn't put anything to the paste buffer but '-c -t' does. That's
logic much easier to add inside of password store than outside of it (
Matthew,
Reasonable enough. Revised patch attached.
I added some further indentation of the subcommand for readability.
Von
On Thu, Feb 13, 2014 at 9:03 PM, Matthew Cengia wrote:
> On 2014-02-13 20:02, Von Welch wrote:
> > Hi,
> >
> > I'm said author of th
Every so often I actually need to look at a password instead of just having
it in my paste buffer. E.g. I need to enter it on another device: a phone,
tablet, Roku box, or some other thing I can't or don't want to run
password-store on. So I run pass and have it put the password to stdout
(e.g. 'pa
My $0.02 after reading all of this is that clearing the clipboard instead
of restoring it makes the most sense.
Having some sort of lock file so that if you quickly (<45 sec apart) run
'pass -c' multiple times, only the last invocation clears the clipboard
might make sense or might be harder than
Here's my version of using 'find' that I've built up to include
directories, not hit on the .gpg extension and other gotchas.
Obviously it's intended for zsh with the argument quoting, but all the find
parts should be portable.
Von
# Search passwords for string and return matches, one per line
s
+1 to Matthew's comments.
I've been using my own find-based functions for a while happily and would
like to understand what tree gets me.
Von
On Apr 14, 2014 10:34 AM, "Matthew Cengia" wrote:
> On 2014-04-14 15:02, Jason A. Donenfeld wrote:
> > Hi folks,
> >
> > We now have the long-desired fin
> * password-store.org
+1
On Thu, Apr 17, 2014 at 7:05 AM, Matthew Cengia wrote:
> On 2014-04-17 13:02, Jason A. Donenfeld wrote:
> [...]
> > * password-store.org
>
> I'd pick this one.
>
> --
> Regards,
> Matthew Cengia
>
> ___
> Password-Store mail
Resubmitting this patch (updated to latest head of git) to add -t/--tail to
'pass show' .
The intent of this patch is to limit outputting of passwords. It works
under the assumption the password is the first line of the file and then
the rest of the file is not/less sensitive.
It works in conjunc
I just took the new 'mv' functionality for a quick spin (nothing terribly
stressfull) and it seems to work well.
I really appreciate having it since I have a bunch of multi-level paths
from my conversation from KeeSafe that I'm slowly moving over to a flatter
hierarchy and it's much nicer than goi
I'd be willing to take a stab at this this weekend if no one else jumps on
it.
I've got no experience with test frameworks for bash scripts. The cgit
make-based one looks simple but reasonable. Google turns up a number of
options. Any opinions welcome.
Von
On Thu, Apr 17, 2014 at 7:37 PM, Jaso
Hi Jason,
I don't have a use case for either of those suggestions. I created --tail
because I kept finding myself running 'pass -c' followed by 'pass' and
dislike printing passwords when not necessary.
It's also not clear to me how they play together. What would 'pass -c -h
xxx' or 'pass -h -t xx
+1 to an option to generate a new password and not replace metadata.
-1 to later suggestions to store password history in the metadata, that's
what git is for. I think writing a script around git to go back and get
previous passwords is the way to address that.
Von
On Fri, Apr 18, 2014 at 2:12
with pass.
>
> --
> Dd
>
> > -Original Message-
> > From: Password-Store [mailto:password-store-boun...@lists.zx2c4.com] On
> > Behalf Of Von Welch
> > Sent: Friday, April 18, 2014 14:28
> > To: Jimmy Neutron
> > Cc: password-store
> > Subject:
cleanly.
Von
On Thu, Apr 17, 2014 at 10:06 PM, Von Welch wrote:
> I'd be willing to take a stab at this this weekend if no one else jumps on
> it.
>
> I've got no experience with test frameworks for bash scripts. The cgit
> make-based one looks simple but reasonab
cide it's not part of the test suite.
4) Going further with regards to interactivity, I have no idea how to test
'pass edit' at this point. I guess one could create a vimscript or
something similar to simulate a user typing? Or just not worry about it for
the test suite.
Von
O
oing further with regards to interactivity, I have no idea how to
> test
> > 'pass edit' at this point. I guess one could create a vimscript or
> > something similar to simulate a user typing? Or just not worry about it
> for
> > the test suite.
> >
>
> How ab
>
> How about just doing something like `EDITOR=magic.sh pass edit`, where
> magic.sh is a shell script that uses sed(1) to modify the password?
>
Worked. Pushed.
Von
On Sat, Apr 19, 2014 at 2:13 PM, Von Welch wrote:
> Hi Lukas,
>
> On Sat, Apr 19, 2014 at 1:52 PM, Luka
>
> I've now made it even simpler with this commit:
>
> http://git.zx2c4.com/password-store/commit/?id=18933a2db9015d2acd669ac879521e02caed0bba
Backed out my changes, pulled this and the prerequisite patch into the
testing branch and seems to work fine. Pushed to github (*).
Von
(*) I assume at
Referring back to the testing thread, I figured out a couple behaviors of
'pass insert' that were confusing me. I suggest these are both bugs.
1) "echo foo | pass insert my-pass" fails, but still creates an empty file.
See appended example 1.
2) "echo foo | pass -e insert my-pass" returns 1 if my
>
> On Sun, Apr 20, 2014 at 8:18 PM, Von Welch wrote:
> 1) "echo foo | pass insert my-pass" fails, but still creates an empty
> file. See appended example 1.
>
> http://git.zx2c4.com/password-store/commit/?id=91ef9dbbea26573414220073dd92bba4b1d4c94a
You fixed t
>
> It'd be nice if you could develop consistent style for $variable vs
> ${variable}, but for the most part, things look okay now.
I tend to use the brackets if I think it makes for easier-to-read code, but
it's fairly subjective and I don't feel strongly. Looks like you prefer the
first form un
>
> On Mon, Apr 21, 2014 at 3:56 AM, Von Welch wrote:
>>
>> You fixed the interactive case, but the following now hangs if the
>> password does not exist:
>>
>> % echo "foo" | ../src/password-store.sh insert my-pass
>>
>> (It also points
> Do people commonly store only a password in their password store DBs?
I'd guess about half of my entries are password-only. (BTW, a common reason
for extra data is for me to store my random answers to security questions).
I agree with both Daniel's diagnosis of the problem and observation there
s point, I just want to make
sure it's not dead before putting in the effort.
Thanks,
Von
On Sat, Jan 11, 2014 at 11:26 PM, Von Welch wrote:
> The attached patch adds a new option to 'show' which is '-t/--tail' which
> causes pass to print the 2nd and subsequen
Hi Phillip,
Thanks for chiming in. Yes, 'pass -c -t ' is basically my default
now, putting the password into the clipboard and all the metadata to
stdout. Once I had this ability, I find it's what I want most of the time
and it's benign the rest.
Part of this, which is a principle I don't think
e:
> On Fri 4 Jul 2014 at 07:16:36AM -0400, Von Welch wrote:
>
> > Thanks for chiming in. Yes, 'pass -c -t ' is basically my
> > default now, putting the password into the clipboard and all the
> > metadata to stdout. Once I had this ability, I find it'
d whistles
that people want by implementing their own front end scripts, and the
desire to keep pass small and simple. Gets back to the original Unix pipe
philosophy by breaking pass down into a more modular structure.
Von
On Wed, Jul 9, 2014 at 11:38 AM, SamLT wrote:
>
>
> On 07/04
I agree with not committing unchanged files. I suspect the best way to
implement it is to look for a change in the modification timestamp of the
temporary file.
Von
On Tue, Sep 23, 2014 at 8:47 AM, Hugo Osvaldo Barrera
wrote:
> I've come across a small issue that can clutter up the log if using
+1 for keychain
On Sep 25, 2014 10:33 AM, "Caleb Marble" wrote:
> > I am trying to use pass with gpg-agent provided by gpgtools on OS X.
> > However when I run init I get the following:
> >
> > You are not running gpg-agent. This means that you will need to enter
> > your password for each and ev
My vim configuration sets a bunch of options which I find generally useful,
but I don't want when editing password files, such as saving backups and
undo information.
Do other folks have this issue and how do they deal with it?
It used to be that password-store used a temporary filename that look
Hi all,
I was able to get it working with a modified version of the plugin at the
gist Eirc pointed. Result at:
https://gist.github.com/von/4f88275aea50c4b33d10
I had to modify the plugin to get it to work for me because (1) OSX has an
'/private' prepended to paths because everything temporary
I attempted at least a couple times last year to get a --tail option added
that would do as you suggest without success. See the email archives, e.g.
http://lists.zx2c4.com/pipermail/password-store/2014-July/001039.html
The opposition to adding such, as I understand it, is a desire to keep
things
FYI, What follows is the zsh function I use to search my password store
based on 'find.' I've tuned it to match any part of directories and stores
(case insensitively), but not the gpg extension or the password store path
or git directory. sed is used to prune the .gpg extension from store files.
>I don’t understand why the „show“ subcommand even shows a tree.
Since you mention it, I will say 'pass [show]' acting differently when
given a file or directory makes it hard to write scripts using it since
unless you look inside the password store to see if the argument is a
directory or file, p
itional security features (such as resetting the clipboard after a
> timeout) you might want to reuse.
>
> On Sun, 2 Aug 2015 at 19:16 Von Welch wrote:
>
>> >I don’t understand why the „show“ subcommand even shows a tree.
>>
>> Since you mention it, I will say &#x
Works fine for me installed via Homebrew.
Von
On Wed, Apr 12, 2017 at 3:49 PM Jp wrote:
> Hello,
>
> Is there any incompatibilities with PASS and MAC OS 10.12.4 (16E195)?
>
> Thank you
> --
> Consider encryption my public key is available for download.
> _
I believe I ran across this trying to use a key that didn't have an email
address associated with it during generation.
Von
On Thu, Feb 22, 2018 at 6:34 PM moritz wrote:
> Dear List,
>
> I'm using pass as my main password manager, but since a few days i can't
> create new passwords, I always ge
45 matches
Mail list logo
