What is wrong with this approach? Pass's method of storing passwords is fairly free-form and unlikely to change, so I don't see why pass would have to provide an abstraction layer on top of it.
On 16 June 2015 16:53:54 CEST, Jean-Baptiste Denis <[email protected]> wrote: >On 06/16/2015 03:16 PM, Jean-Baptiste Denis wrote: > >> Do you have a clever way to achieve this ? > >If you're using git you can configure an alias, but it still feels >wrong to me =) > >$ pass git config --local alias.printing '!find . -type f -name "*gpg" >-print0 >-exec gpg -d --batch -q {} \; | tr "\0" " "' > >$ pass git printing >server1 euj7mazeek5ieRoo >server2 ohgaiKohfeis7iiK >... > >Jean-Baptiste > > > >_______________________________________________ >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
