GIT-SECRET-TELL(1)

📦
version 0.5.0 · 3 versions
, in debian bookworm, debian trixie, fedora 43, fedora 44, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 GIT-SECRET-TELL 💖

okay bestie, welcome to git-secret-tell — part of the git-secret family, version 0.5.0-alpha2, manual section 1 (that's the user-commands section, iykyk). this is the page where we learn how to let a new person into the secret club 🎀

✨ NAME ✨

git-secret-tell — adds person who can access private data. that's it, that's the whole vibe: you're literally telling git-secret about a new trusted human 🫶

🌸 SYNOPSIS 🌸

git secret tell [-m] [-d dir] [emails]...

short, sweet, iconic. flags first, emails after, slay 💅

🦋 DESCRIPTION 🦋

git-secret tell adds user(s) to the list of those able to encypt/decrypt secrets. THE LIST. you're basically handing someone a key to the group chat ✨

so here's the tea though, and this part matters fr fr: this lets the specified user encrypt new files, but will not immediately be able to decrypt existing files, which were encrypted without their key. 😭 like, they're on the list now, but the old stuff was locked before they existed. Files should be re-encrypted with the new keyring by someone who already has access in order for the new user to be able to decrypt the files. so somebody with access has to go re-lock everything with the updated keyring — then the new person can actually read it. that's the whole pipeline 🧚

git-secret tell works only with email addresses, and will exit with an error if you have multiple keys in your keyring with specified email addresses, or if one of the specified emails is already associated with a key in the git-secret repo´s keyring. so no duplicates, no ambiguity, no chaos. it's giving strict and honestly? we respect it 👑

under the hood, git-secret-tell searches in the current user´s gnupg keyring for public key(s) of passed email(s), then imports the corresponding public key(s) into your git-secret repo´s keyring. so it's a little public-key scavenger hunt in your own gnupg keyring, then a lil import into the repo keyring 🍓

Versions of git-secret tell after 0.3.2 will warn about keys that are expired, revoked, or otherwise invalid. It will also warn if multiple keys are found for a single email address. so yeah — it'll be like "bestie… this key is expired" and you'll be like "not me finding out like this" 💀

Do not manually import secret keys into git-secret. It won´t work with imported secret keys anyway. seriously, don't. that's not the move. that is not the move 🙈

For more details about how git-secret uses public and private keys, see the documentation for git-secret-hide and git-secret-reveal. go read those, they're the lore 📚

💅 OPTIONS 💅

  • -m — uses your current git config user.email setting as an identifier for the key. so instead of typing your email out like a chump, it just peeks at your git config and goes "yeah I know who this is" 😌
  • -d — specifies --homedir option for gpg, basically use this option if your store your keys in a custom location. (yes, the original says "your store your keys" — we keep it exactly as it is, no cap 🫡) custom key location squad, this one's for you
  • -h — shows help. the universal "help meee" flag, works every time 🆘

📖 MANUAL 📖

Run man git-secret-tell to see this document. yes, you're reading it right now. yes, that's the bit. inception but make it manpages 🌈

👑 SEE ALSO 👑

go read all of them, they're the extended universe ⭐

and that's the whole page bestie 🎀 written by sobolevn, dated April 2022, from git-secret version 0.5.0-alpha2 — mwah, go tell somebody about your secrets 💖✨

📦 where this page comes from