Salta al contenuto principale


The idea of a "pass" compatibility layer for "sopass" has been suggested. I'm thinking that the following would cover most common uses:

* "pass" and "pass list"
* "pass NAME" and "pass show NAME"
* "pass insert" and "pass insert -m"

Do you use the pass (password-store) command line password manager? Do you have a common invocation that isn't one of the above? What is it?

in reply to Lars Wirzenius

"sopass" is my command line password manager, similar to "pass", but different. Biggest difference is that it's written around the stateloss OpenPGP specification, but also the way it stores secrets and the command line interface are different.

I don't need a compatibility layer but I've been told it'd help other people.

in reply to Lars Wirzenius

Why can’t upstream “pass” support a sop interface? Adding that support seems simpler to do than a rewrite with a compatibility layer? I haven’t looked at the pass code, though, so I may be missing other reasons for doing a rewrite.
in reply to Simon Josefsson

@jas You should probably ask that from the people developer or maintain pass. I have nothing to do with pass. Its dependence on GhuPG is only one reason why I want a new tool.
in reply to Lars Wirzenius

pass edit, pass otp (either via github.com/tadfisher/pass-otp or because my "pass" is actually gopass)
in reply to Lars Wirzenius

`pass show -c` (send password to clipboard) is my most invoked one, I also regularly use `pass edit` for multiline stuff as Evgeni mentioned
in reply to Lars Wirzenius

"pass edit" fairly frequently. "pass generate". Plus I have the extension for "pass otp".

I could adapt to a different interface, though, if there were a reason to do so — why would I want to switch away from pass?

in reply to Jonathan Corbet

@corbet I don't know why others would switch away from pass, but for me the reasons are, roughly in order:

* I would like not be locked into using GnuPG, or any other OpenPGP implementation
* I am wary of a long, complicated Bash script, even if it has worked fine for years
* I don't want to try to debug or improve such a script (BTDT)
* I don't like that names for secrets are in cleartext with pass

I think pass is an amazing tool, but I would prefer not be amazed by my fundamental tools.

in reply to Lars Wirzenius

i use pass generate -c -n, pass init (to re-encrypt files), .gpg-id files, pass [show] -c, pass rm/mv, pass git, pass otp
in reply to anarcat

@Anarcat I'm writing sopass.liw.fi/ but it will not have on-disk store compatibility, since I don't like the pass one. There's a conversion script, though (mostly untested).
in reply to Lars Wirzenius

"pass -c", generate and edit are the most used. Using gopass and also the android app.
in reply to Lars Wirzenius

gopass also supports pluggable backends for the crypto with gpg and age currently supported so a sopass backend could be added there as well.
in reply to Lars Wirzenius

A little while ago I asked here how people most commonly invoke pass, the command line password manager. I want to consider adding a compatibility layer to my own command line password manager, but I don't want to re-implement the full pass interface. I'm too lazy to do that in my free time.

A summary of the responses: the most common sub-commands mentioned:

* edit
* -c, show -c
* otp (an extension)
* generate
* rm
* mv
* git

Most of those would be easy to implement. I'll ponder.

in reply to Lars Wirzenius

You might want to consider adding a subcommand for when you want to add or delete a gpg key and want to reencrypt the lot.
In general I find that pass is amazing and works really well, even without a compatibility layer ;-)

Questo sito utilizza cookie per riconosce gli utenti loggati e quelli che tornano a visitare. Proseguendo la navigazione su questo sito, accetti l'utilizzo di questi cookie.