Ever since I started using mutt, I've been using the venerable 'pass' utility to store my passwords and the like.
I'm grateful that it exists, it means that people with a 100% floss stack can store their secrets.
But I find it to be a FAFF to get going on a new machine. I must:
- Figure out how to get my GPG keys re-established
- Drag the pass files over
- Ensure they're all in sync and happy
Yes, I'm a whimp, but this is a LOT. Given that I use @1password for the rest of my secrets keeping and L-O-V-E it to bits, I'd rather use it for this as well.
But when I last looked, the 1Password CLI was - primitive. You had to reference secrets by item id. Ungh. Error prone and painful.
They've fixed it!!!
https://developer.1password.com/docs/cli/secret-reference-syntax/
Now you can use logical reference paths to access your secrets, so lazy bums like me can shove:
export EVILCORP_API_KEY="$(op read 'op://my_vault/Evilcorp API Key/credential')"
into my dot files and away we go!
Well done #agilebits this is excellent work!