| ▲ | blop 3 hours ago | |
fnox (https://fnox.jdx.dev/) is another solution which is also fantastic for day-to-day human use in the cli. It works a bit like sops but can also chain multiple encryption providers, so for example you can use an encrypted age key with a fido2 provider (a yubikey for example) as the main provider of all the secrets on your computer. If you run for example `fnox exec gh`, fnox will ask you to touch the yubikey to decrypt the age key and decode the github token env var for the gh cli (fnox can also cache the decoded value for a bit, like gpg agent). You can tell the AI agent to use `fnox exec gh` to access gh without seeing the gh token. Or create a shell alias so it's transparent. It also has an MCP server and proxy server to filter API calls to remote APIs (I haven't tried that yet) it supports quite a few providers (https://fnox.jdx.dev/providers/overview.html): age, fido2, AWS, Azure, Google, kubernetes secrets, vault/openbao, 1password, bitwarden, keepassxc, etc. A lot of them are read/write so you can also use fnox to sync secrets across different systems. | ||