Skip to content

Lock database credentials - #23

Merged
scheibling merged 2 commits into
mainfrom
security/misc-security-improvements
Nov 16, 2026
Merged

scheibling merged 2 commits into
mainfrom
security/misc-security-improvements

Conversation

@scheibling

@scheibling scheibling commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Previously, database credential sets were not locked to the host that was specified in the agent-side profile.

With this, the server can no longer arbitrarily change the target of a backup job using an agent-side profile to leak the credentials

Might lead to breaking changes, needs a new minor release


Also fixes #20 with a manual confirmation before deleting a key that is in use in historic backups, and patches the hole around listing target names for individual keys

@scheibling
scheibling merged commit 0a7bcb7 into main Nov 16, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deleting a key ring might lead to data loss

1 participant