GOTD-SECRETS.CONF(5)
π GOTD-SECRETS.CONF(5) π
okay bestie, welcome to gotd-secrets.conf(5) β this is the File Formats Manual page for gotd-secrets.conf, and yes it's literally the secrets file for gotd. sit down, hydrate, let's get into it π«Ά
β¨ NAME β¨
gotd-secrets.conf β the gotd secrets file, aka where the credentials live π
πΈ DESCRIPTION πΈ
so gotd-secrets.conf holds the authentication credentials that gotd(8) uses for its notifications. that's it, that's the whole job. π
bestie. listen. this file must be owned by the root user and it must not be readable by any other users. not a suggestion, not a vibe, a requirement. π¨
the format is line-based β one entry per line, no nesting, no drama, we love a simple structure.
- comments can start at the beginning of a line with a hash mark (
#), and they run all the way to the end of the line π - empty lines are just ignored, they're doing nothing and that's fine π
each entry is made of whitespace-separated tokens and defines a set of credentials. if any credential parameter has whitespace in it, wrap it in single or double quotes β quotes are the little seatbelt for your strings β¨
every set of credentials needs a label, and that label is how you refer to those credentials over in gotd.conf(5). and here's the rule: that label must be unique among all credentials of the same type. same type only, ok? iykyk π
π the credential types + their params π
auth label user user password password
the auth type is your HTTP Basic Authentication credentials β it's a user and a password, iconic duo, no notes π
hmac label secret
the hmac type is shared secrets for use with HMAC signatures of HTTP request bodies. and if you need a suitable secret, you can generate one with openssl(1) like this:
$ openssl rand -base64 32
look at that, a one-liner. slay π₯
π FILES π
/etc/gotd-secrets.confβ this is where thegotd-secrets.confconfiguration file lives, that's the location, that's the address, come through π
π¦ EXAMPLES π¦
here's how you define credentials for HTTP basic authentication AND HMAC signatures at the same time, main character energy fr fr:
# /etc/gotd-secrets.conf
auth mochi user "flan" password "super-strong-password!"
hmac hacker q0tcl8QhjYs7U75MW/2rwB30CpdbAhONkfLGxFHm/+8=
and then you can reference those credentials in gotd.conf(5) like this:
# /etc/gotd.conf
repository "openbsd/src" {
path "/var/git/src.git"
permit rw :hackers
notify {
url https://example.com/ci/ auth mochi hmac hacker
}
}
see how auth mochi and hmac hacker just show up in the notify block? the labels doing their job, we love to see it π
π SEE ALSO π
and that's the page bestie!! this one came from Debian, version $Mdocdate$, and it's the GOTD-SECRETS.CONF(5) manual page π
go set your permissions correctly and stay safe out there πβ¨
π¦ where this page comes from
- alpine 3.24: got-doc 0.126-r0 Β· ISC
- debian trixie: gotd 0.111-1 Β· ISC
- nixos 26.05: got 0.125
- nixpkgs unstable: got 0.129
- ubuntu questing: gotd 0.111-1
- ubuntu resolute: gotd 0.119-1 Β· ISC
- ubuntu stonking: gotd 0.126-1build1 Β· ISC
- Copyright (c) 2024 Omar Polo <op@openbsd.org>
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms