Your key stays on your phone.
kudde holds an SSH key that opens your machines. This is how it guards that key, what an alert carries, how releases are signed, and how to report a problem.
The phone key
Made in secure hardware
The SSH key is made in the Android Keystore, in StrongBox where the phone has it. It cannot be exported and never leaves the phone.
Yours to unlock
It signs only for 30 minutes after you unlock the phone or use your fingerprint. Alerts never need it.
Only herdr-core
The line you place in
authorized_keyslets the key run only herdr-core: no shell session, no forwarding. herdr-core can still run commands as your user, so treat the key like a shell login.Host keys checked
You confirm each machine’s host key once, and a changed key stops the connection.
Alerts
What an alert carries
The agent’s name, the machine, its state, the kind of request, and the time. Never the screen’s text or the agent’s message.
What ntfy sees
Only ciphertext. Each push is encrypted for the phone with web push encryption (RFC 8291) and padded to one size, so its length says nothing either.
A token that only writes
kudde-push uses a dedicated ntfy user that may only write to
up*topics, never read. It sends pushes only to the servers its config allows, and its token nowhere else.No Google
Alerts go through your own ntfy server to the ntfy app on the phone, with UnifiedPush. No Google service is involved.
Releases
Signed in the open
Releases are built and signed by GitHub Actions in the public repository. The release workflow publishes nothing unless the APK’s certificate matches the fingerprint kept in the repository.
Checked by you
Check the first install against that fingerprint. After that, Android refuses an update signed with any other key. kudde-push is signed too, and
ssh-keygenchecks it.Installed by hand
With background installing off in Obtainium, nothing installs on its own: you install each update after checking it.
Reporting a problem
Please don’t open a public issue. Report it privately instead, with report a vulnerability on GitHub. Only the maintainer sees it.
Say what you found, which versions of kudde and herdr-core it affects, and how to reproduce it. Leave out your own host names, IP addresses, ports, paths and keys; a made-up example shows the problem just as well.
You’ll get a first reply within a week. Once a fix is out, the advisory is published, with credit to you if you’d like.
Only the latest release gets security fixes, so update to it before reporting. Problems in herdr-core, in herdr or in your ntfy server belong to those projects.