This is a very elegant approach. I really like it. But it's also a huge limitation for third party tools who would like to share data through pass. I mean I currently use both the firefox addon and dmenu script. And I think it make sens to delegate format management to pass to ensure compatibility The main question behind this is : what is the purpose of pass ? * to be a command line passwords tool ? * or to be a command line based password manager facilitating access to password data to third tools ?
*-------- Johan Venant.* Tel : +33 6 13 06 95 43 *www.invicem.pro <http://www.invicem.pro>* On Tue, Apr 29, 2014 at 4:18 PM, Alexis <[email protected]> wrote: > Hi, > I prefer pass to stay agnostic to the user data format, > since I also use it for storing secure notes. > > If I would desire a structure for certain passwords, > I'd add that structure (e.g. JSON) to those password files > and then extract it through a unix pipe (e.g. jq¹). > > Or event simpler if the first line is the password (for use with -c) > and second and last line is the username I could use: > % pass path/to/login | tail -1 | pbcopy > > I would much appreciate it if pass would stick > to the Unix philosophy, it makes it so versatile for me. > > > Cheers, > Alexis > > > ¹ http://stedolan.github.io/jq/ > _______________________________________________ > Password-Store mailing list > [email protected] > http://lists.zx2c4.com/mailman/listinfo/password-store >
_______________________________________________ Password-Store mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/password-store
