Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Imho, plain text is the optimal way to store passwords and related meta data. Before pass became popular I started with my own 'plain text pw store', while converting from some db backed $PWSTORE, which became obsolete. So now I'm happy to have it all in a single text file with some markup around. Editing is done with some vim settings like folding, not showing passwords and pushing entries to the clipboard.

And here lies the difference. What I was not able to do this with pass: I think I use xclip, which detects if the clipboard was used, after which the pw is removed from the clipboard. No timeout. This enabled me to consecutively send a list of strings to the clipboard. E.g 1. Send URL, 2. Username, 3. Secret. Recently, I added TOTP support.

I think pass is not able to do this. I would like to convert over to pass, but my established workflow is to convenient. Well, I haven't checked all the extensions of pass though. Otoh, I would not like to write an extension of my own.

Perhaps, pass supports similar functionality now?



I'm pretty sure `pass edit foo` does more or less what you seek: it launches $EDITOR with the full contents of whatever's in foo, and would therefore naturally support whatever markup or editor shenanigans you want for your preferred workflow. Or `pass show foo`, which you could pipe any which way for whatever processing you see fit.


Nice! Your suggestion is particularly helpful. Thanks a lot. I can envision this might work.


I'm using gopass, which is a mostly API compatible alternative to pass written in go. It definitely has support for xclip/wl-clip.


I'm now using gopass as well, and it's great! Especially with https://github.com/gopasspw/gopassbridge, I get browser auto complete. And https://play.google.com/store/apps/details?id=dev.msfjarvis.... on Android with its password fill integration. It's the best of all worlds and entirely free.

I even have my wife set up with the android app just in case something happens to me or she needs common passwords. She doesn't use it for her passwords yet, but baby steps.


It would be really easy to implement this, as a wrapper around pass.


> Perhaps, pass supports similar functionality now?

It does. I use it every day.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: