-
-
Notifications
You must be signed in to change notification settings - Fork 268
feat: switch to include directives in pg_hba #1765
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
staaldraad
wants to merge
7
commits into
develop
Choose a base branch
from
etienne/sec-493-switch-pg_hba-to-use-include-directive
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
d9f379b
feat: switch pg_hba to use include directives
staaldraad 3ec10cb
chore: update ansible regex
staaldraad 29d3add
fix: psql_version not complete
staaldraad e34cf16
fix: pgbouncer doesn't need access
staaldraad 1c86658
fix: rebase
staaldraad 921e4b4
fix: gate pg_hba includes on PG_VERSION in Dockerfile-supabase
brainrake ef0a2a9
Merge branch 'develop' into etienne/sec-493-switch-pg_hba-to-use-incl…
staaldraad File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,95 @@ | ||
| # PostgreSQL Client Authentication Configuration File | ||
| # =================================================== | ||
| # | ||
| # Refer to the "Client Authentication" section in the PostgreSQL | ||
| # documentation for a complete description of this file. A short | ||
| # synopsis follows. | ||
| # | ||
| # This file controls: which hosts are allowed to connect, how clients | ||
| # are authenticated, which PostgreSQL user names they can use, which | ||
| # databases they can access. Records take one of these forms: | ||
| # | ||
| # local DATABASE USER METHOD [OPTIONS] | ||
| # host DATABASE USER ADDRESS METHOD [OPTIONS] | ||
| # hostssl DATABASE USER ADDRESS METHOD [OPTIONS] | ||
| # hostnossl DATABASE USER ADDRESS METHOD [OPTIONS] | ||
| # hostgssenc DATABASE USER ADDRESS METHOD [OPTIONS] | ||
| # hostnogssenc DATABASE USER ADDRESS METHOD [OPTIONS] | ||
| # | ||
| # (The uppercase items must be replaced by actual values.) | ||
| # | ||
| # The first field is the connection type: "local" is a Unix-domain | ||
| # socket, "host" is either a plain or SSL-encrypted TCP/IP socket, | ||
| # "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a | ||
| # non-SSL TCP/IP socket. Similarly, "hostgssenc" uses a | ||
| # GSSAPI-encrypted TCP/IP socket, while "hostnogssenc" uses a | ||
| # non-GSSAPI socket. | ||
| # | ||
| # DATABASE can be "all", "sameuser", "samerole", "replication", a | ||
| # database name, or a comma-separated list thereof. The "all" | ||
| # keyword does not match "replication". Access to replication | ||
| # must be enabled in a separate record (see example below). | ||
| # | ||
| # USER can be "all", a user name, a group name prefixed with "+", or a | ||
| # comma-separated list thereof. In both the DATABASE and USER fields | ||
| # you can also write a file name prefixed with "@" to include names | ||
| # from a separate file. | ||
| # | ||
| # ADDRESS specifies the set of hosts the record matches. It can be a | ||
| # host name, or it is made up of an IP address and a CIDR mask that is | ||
| # an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that | ||
| # specifies the number of significant bits in the mask. A host name | ||
| # that starts with a dot (.) matches a suffix of the actual host name. | ||
| # Alternatively, you can write an IP address and netmask in separate | ||
| # columns to specify the set of hosts. Instead of a CIDR-address, you | ||
| # can write "samehost" to match any of the server's own IP addresses, | ||
| # or "samenet" to match any address in any subnet that the server is | ||
| # directly connected to. | ||
| # | ||
| # METHOD can be "trust", "reject", "md5", "password", "scram-sha-256", | ||
| # "gss", "sspi", "ident", "peer", "pam", "ldap", "radius" or "cert". | ||
| # Note that "password" sends passwords in clear text; "md5" or | ||
| # "scram-sha-256" are preferred since they send encrypted passwords. | ||
| # | ||
| # OPTIONS are a set of options for the authentication in the format | ||
| # NAME=VALUE. The available options depend on the different | ||
| # authentication methods -- refer to the "Client Authentication" | ||
| # section in the documentation for a list of which options are | ||
| # available for which authentication methods. | ||
| # | ||
| # Database and user names containing spaces, commas, quotes and other | ||
| # special characters must be quoted. Quoting one of the keywords | ||
| # "all", "sameuser", "samerole" or "replication" makes the name lose | ||
| # its special character, and just match a database or username with | ||
| # that name. | ||
| # | ||
| # This file is read on server startup and when the server receives a | ||
| # SIGHUP signal. If you edit the file on a running system, you have to | ||
| # SIGHUP the server for the changes to take effect, run "pg_ctl reload", | ||
| # or execute "SELECT pg_reload_conf()". | ||
| # | ||
| # Put your actual configuration here | ||
| # ---------------------------------- | ||
| # | ||
| # If you want to allow non-local connections, you need to add more | ||
| # "host" records. In that case you will also need to make PostgreSQL | ||
| # listen on a non-local interface via the listen_addresses | ||
| # configuration parameter, or via the -i or -h command line switches. | ||
|
|
||
| # TYPE DATABASE USER ADDRESS METHOD | ||
|
|
||
| # trust local connections | ||
| local all supabase_admin scram-sha-256 | ||
| local all all peer map=supabase_map | ||
| host all all 127.0.0.1/32 trust | ||
| host all all ::1/128 trust | ||
|
|
||
| # IPv4 external connections | ||
| host all all 10.0.0.0/8 scram-sha-256 | ||
| host all all 172.16.0.0/12 scram-sha-256 | ||
| host all all 192.168.0.0/16 scram-sha-256 | ||
| host all all 0.0.0.0/0 scram-sha-256 | ||
|
|
||
| # IPv6 external connections | ||
| host all all ::0/0 scram-sha-256 | ||
|
|
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| host all all 0.0.0.0/0 scram-sha-256 | ||
| host all all ::0/0 scram-sha-256 |
11 changes: 11 additions & 0 deletions
11
ansible/files/postgresql_config/pg_hba_users_public.conf.j2
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| host all pgbouncer 0.0.0.0/0 scram-sha-256 | ||
| host all supabase_admin 0.0.0.0/0 scram-sha-256 | ||
| host all supabase_auth_admin 0.0.0.0/0 scram-sha-256 | ||
| host all supabase_storage_admin 0.0.0.0/0 scram-sha-256 | ||
| host all supabase_replication_admin 0.0.0.0/0 scram-sha-256 | ||
|
|
||
| host all pgbouncer ::0/0 scram-sha-256 | ||
| host all supabase_admin ::0/0 scram-sha-256 | ||
| host all supabase_auth_admin ::0/0 scram-sha-256 | ||
| host all supabase_storage_admin ::0/0 scram-sha-256 | ||
| host all supabase_replication_admin ::0/0 scram-sha-256 |
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm... this hard-codes all configuration file names so if a downstream user (projects that use these Dockerfiles to create their own, for example Multigres), additional files cannot be added easily. There is probably also going to be problems if any files need to be added, renamed, or removed since file names are hard-coded.
A more flexible approach is to create a directory
pg_hba.conf.d(following Debian convention for configuration directories) and just use aninclude_dirdirective. In that case, files can be added and removed at will and will not generate any errors.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes sense. At the time, I was concerned in ensuring the correct order, I think I did initially misunderstand the following from the docs:
(originally left
pg_hba_public.confto always exist which was incorrect and allowedsslmode=disableto skip past the ssl enforced because there was a match forhost ....)I'll see about doing this with the
include_dir- it needs some Supabase internals changes to understand apg_hba.conf.dbut not a big deal