@natch, I actually saw that and thought it was the same thing I was building. So I thought someone beat me to the punch.
The projects look similar, but georgebrock/1pass is a CLI to 1password db itself. It doesn't do anything to render the UI or anything like that. With sudolikeaboss, I don't actually decrypt any of the password data stored on your machine. I actually call to the undocumented API for the local 1password daemon. So it took a small amount of reverse engineering to get to this point.
In terms of age, I have actually been using a prototype of sudolikeaboss, written in Node, for several weeks.
Hope that is clear! I wouldn't ever want to say I'm using someone else's idea! I think georgebrock's 1pass is an awesome project. I also intend to port it to Go at some point. When that is done, I promise I won't say it's my own work. :)
Great point! I mulled over this for a while, but couldn't come up with a general name that was adequately light-hearted for me. Originally, I named the project `termpass` an obvious portmanteau on terminal and 1password (or I guess just password). That name seems pretty stale though. `sudolikeaboss` just seemed like a fun name that was particularly direct about the core use-case for which it was designed.
You make an excellent point. I did not, in any way intend to offend Windows users. I was merely trying to be "tongue-and-cheek"-y with my comment. Really, I wouldn't know how to make this work well for an admin on windows. Last I used windows to SSH I was using putty, but that was back in 2005. I have since completely moved from using Windows to *nix systems.
As far as Linux support goes, I had planned to take a stab at writing a tmux plugin so that could potentially get me in the door to supporting Linux.
All that said, I am updating my README to address some of these concerns. Thanks so much for the great feedback!
Creator here! I'd love any comments if anyone has them. This project is particularly useful for me so I was hoping others would find great use for it as well :)
I think it's been iterated before, but in the future we intend to open source our key serving software. There's still much work to be done on that front. We love PGP's crypto, but we found a few problems with it in general:
1) It's hard for the normal person. (The user experience for PGP is just horrendous)
2) Before you send an email to someone you have to know their public key.
With that said, we have done some research on integrating PGP like public key encryption along with our current key serving mechanism. With public key, using Virtru will be essentially equivalent to holding the keys yourself. Look for more of this in the future :-)