fix: add missing REVOKE on config-write functions#64
Merged
Conversation
These two config-write functions were missing REVOKE ALL ... FROM PUBLIC, allowing any database user to modify global and per-group configuration. All other management functions already had this protection. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
set_config()andset_group_config()were missingREVOKE ALL ON FUNCTION ... FROM PUBLIC, allowing any database user to modify global and per-group pipeline configurationTest plan
make check-regression TEST=acl— verifiesset_configandset_group_configare denied for non-superusers, andget_config/get_group_configremain accessible🤖 Generated with Claude Code