Easy Sharing and Encryption Tools
OP, the 1Password CLI
The 1Password CLI tool, op https://developer.1password.com/docs/cli/ is a very useful tool for integrating the 1Password tool with your CLI workflows and other tools. You can, for example, easily incorporate secrets stored in 1Password in shell scripts as special URLs that will be resolved at run-time by 1Password, getting your MFA tokens if necessary. It also has many plugin tools to wrap common development tools like psql that need secrets. The 1Password app also comes with an SSH agent to manage your keys, and integrates with GitHub to sign your commits.
AWS Vault
aws-vault is a tool that stores your AWS credentials in your OS system secrets store (or another store, such as 1Password via the op CLI tool), and can run AWS CLI commands and tools that use
the AWS SDK in a subshell, making the credentials available temporarily as command-line variables.
AWS Vault and 1Password can work together to provide a CLI-compatible MFA solution. For example, when I wish to run a command in the Production environment, I have to double-tap the button on the side of my Apple Watch to verify that I’m who I say I am (and have been since I put the watch on and verified myself).
https://github.com/99designs/aws-vault
Age
For sharing temporary secrets from dev to dev that don’t need to be stored anywhere for very long, I have found that this tool is very good. https://github.com/FiloSottile/age It’s just a general encryption tool that’s an easy replacement for PGP for most simple encryption tasks. If you scroll to the bottom of the README, you’ll see that there’s a very simple one-line formula for encrypting a file to send to a developer using the public key they’ve registered in GitHub, which GitHub shares at a specific URL. I can say, for example:
$ curl https://github.com/carloscuba.keys | age -R - your_temporary_credentials.yaml > your_temporary_credentials.yaml.age
And share that file in Slack. Carlos (in this example) could run this to retrieve it:
$ age -d -i ~/.ssh/id_ed25519 your_temporary_credentials.yaml.age > your_temporary_credentials.yaml
It’s a nifty tool to use if:
- the secret is temporary, and doesn’t need to be stored anywhere
- the recipient is a GitHub user with a public SSH key If either of those is false, 1Password is probably the best solution for sharing secrets.
Sops
There are a lot of tools that integrate with age. sops, for example, is a tool for encrypting secrets in configuration files. There’s a Helmsman plugin that integrates with it that I used at my last company, so we could check encrypted secrets into GitHub; devs would be able to write new secrets, but not read existing secrets; and the decryption key was shared only with the CI tools. I don’t know if Terraform has something similar.
https://github.com/getsops/sops
Security
MacOS comes with an obscure little CLI tool called security . Here is its documentation. It allows access to your system keyrings. There is also a graphical tool called “Keychain Access”, but it is hidden in recent versions of MacOS. You need to use Spotlight (the icon in your status bar) to search for it.
Here is a command I can use to see the password I put in the vault for the Mandrilla email debugging app I wrote.
security find-generic-password -a default -s Mandrilla -g