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?

"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.

@liw pass edit (sometimes) and pass -c

@liw 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.

@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.

@liw "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?

@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.

@liw 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

@Anarcat I'm writing https://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).

@liw I second pass edit, pass git (push) and the otp plugin

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.