[02:11:07] <legoktm>	 brett: from https://phabricator.wikimedia.org/T298194, "[Moritz] has plans to replace pwstore entirely"
[02:11:35] <brett>	 bd808: Thanks for the explanation! And thanks for the revert, my apologies.
[02:11:55] <brett>	 legoktm: Aha, thanks!
[02:14:11] <legoktm>	 at work we use https://github.com/mozilla/sops, which is roughly the same as pwstore but supporting more things
[02:20:55] <brett>	 legoktm: As I'm unfamiliar with the pwstore process past the wiki article, I may be speaking too far out of my experience here, but the pws code suggests that sops would be an ideal replacement.
[02:21:21] <brett>	 AFAICT pws pretty much acts like `pass` but also has some convenience wrapping around e.g. git commands
[02:22:47] <legoktm>	 from my experience, I think so too. I don't know if Moritz had anything more in mind than a simple tooling change for this though
[02:23:18] <legoktm>	 at the time that ticket was filed, I had suggested using `age` rather than PGP because it could use SSH keys for encryption, and we already have a process/workflow for managing and revoking SSH keys
[02:23:54] <brett>	 legoktm: But how else will we continually experience the world's worst interface if we don't use GPG? ;)
[02:24:12] <legoktm>	 🙃
[02:26:13] <legoktm>	 former WMFer Lars is working on `sq`, which is supposed to be a reasonable CLI for dealing with PGP than GPG ever was: https://sequoia-pgp.org/blog/2022/03/02/202203-sq-json-1/
[02:27:34] <brett>	 Indeed, and I just posted a comment in that ticket: Arch Linux is tackling a somewhat similar issue and are also using sequoia: https://gitlab.archlinux.org/archlinux/archlinux-keyring
[02:28:38] <legoktm>	 interesting! also, I can see the git repo, but I get a 404 on your issue link, do I need to be logged in to see it?
[02:29:48] <brett>	 oh dangit, I didn't think about that.... Yes you do :(
[02:31:51] <legoktm>	 another time then :)
[02:32:38] <brett>	 I edited the comment to include the paragraphs of note in the ticket