OkcAgent VS SecureStore

It's a bit complicated, but you can use GPG for this! You can follow this guide to setup GPG, and follow this issue to set it up with Termux, then use OKCAgent's GPG function to en/decrypt any files. You can then use any CLI TOTP program and de/encrypt the key files with your GPG key. It's not as secure as having them on the key, as the private keys for the TOTP have to be in your phone's RAM. You can write a shell script for that and put a widget to it on your home screen.

[1]: https://github.com/DDoSolitary/OkcAgent

Simple password decrypt: okc-gpg -d ~/.password-store/mypass.gpg

I made a termux shortcut (button on homescreen) to emulate pass-dmenu via this ( store in ~/.shortcuts):

  #!/data/data/com.termux/files/usr/bin/env bash

Have you looked into NeoSmart's SecureStore? It uses a versionable json file with encrypted strings as secrets, and can be unlocked via a password or a keyfile that you deploy to your application. I've used it before, and it's pretty easy to use and implement. https://github.com/neosmart/SecureStore

A similar but actually secure alternative to user secrets in-prod is using SecureStore: https://github.com/neosmart/SecureStore

Have you looked into SecureStore (https://github.com/neosmart/SecureStore) for managing secrets? You can commit the json file to git, but you keep the key separate.

I tend to use secure store for this. https://github.com/neosmart/SecureStore. json file hold the encrypted stuff and I use a key file that goes out with deployment but never checked in. I can think of a thousand holes for all solutions. Most fall on how to you protect the key or the environment. At that point all is lost.