Pierre,
I think that is a cool idea. In my opinion, username/password entry is
something passmenu should be able to do. Since people store that information in
various formats, it should support the most common ones.
What do you think about this signature:
passmenu [--type [--userfield fieldname | --passwordfile passwordfile
--usernamefile usernamefile] ] [dmenu arguments...]
Here the user would enter something like:
passmenu --type --passwordfile password --usernamefile username [dmenu
arguments...]
Using this invocation, we would want the list of possible selections to only
include directories (not the *.gpg files). So, as in your example, the user
would be prompted with the following in dmenu:
* accounts/google.com
* accounts/protonmail.com
* social/facebook.com
* ...
Instead of:
* accounts/google.com/password
* accounts/google.com/username
* ...
And dmenu would read from the appropriate password/username files.
________________________________
From: Pierre Penninckx <[email protected]>
Sent: Monday, July 24, 2017 5:05:18 PM
To: Matthew Snider
Cc: [email protected]
Subject: Re: passmenu: optionally type username as well
What do you think of using a convention to name the password files instead?
For example, instead of having both username and password under the same
password file:
folder/google.com<http://google.com>
You would have two password files, each one line:
folder/google.com/username<http://google.com/username>
folder/google.com/password<http://google.com/password>
This has the neat feature that it's extendable to any new field without
changing pass.
Le 23 juil. 2017 09:52, "Matthew Snider"
<[email protected]<mailto:[email protected]>> a écrit :
My original code has a mistake. It should call read twice instead of using \n
as a delimiter (e.g. read -r pass; read -r -d '' rest). I think it would be
best for me to test it out over the next week.
In the mean time, if anyone gets around to looking at it, let me know what you
think!
________________________________
From: Password-Store
<[email protected]<mailto:[email protected]>>
on behalf of Matthew Snider
<[email protected]<mailto:[email protected]>>
Sent: Sunday, July 23, 2017 4:03:00 PM
To: [email protected]<mailto:[email protected]>
Subject: passmenu: optionally type username as well
This sender failed our fraud detection checks and may not be who they appear to
be. Learn about spoofing<http://aka.ms/LearnAboutSpoofing>
Feedback<http://aka.ms/SafetyTipsFeedback>
Hi!
I've just recently started using pass and more specifically passmenu, and am
very pleased with it :-)
The main feature I found that was immediately missing when switching over from
keepassx, is the ability to autotype a username/password combination. I read
through the mailing list archives and found this feature was already attempted
here:
https://lists.zx2c4.com/pipermail/password-store/2015-December/001834.html<https://lists.zx2c4.com/pipermail/password-store/2015-December/001834.html>
It doesn't seem like there was any response to this, but arbitrarily taking the
second line doesn't seem ideal to me. I think my implementation is an
improvement, because it leverages the suggested file format of "key: value"
pairs after the first line.
In the included patch you will see that I've just added a --userfield flag
which can be used as follows:
passmenu --type --userfield username [dmenu arguments...]
This corresponds to files which look like:
passw0rd
username: matt.snider
I personally use this by binding $mod+p to the regular passmenu invocation, and
$mod+Shift+p to the invocation using --type and --userfield. This has been
working very well for me.
Please let me know what you think and if you have some feedback.
Best,
Matt
_______________________________________________
Password-Store mailing list
[email protected]<mailto:[email protected]>
https://lists.zx2c4.com/mailman/listinfo/password-store
_______________________________________________
Password-Store mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/password-store
