-
Notifications
You must be signed in to change notification settings - Fork 209
Correct handling of SSL mode always for PostgreSQL #1413
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
Merged
Merged
Changes from 3 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
0caafab
Improved TLSTest to cover more cases
pendula95 eea74e3
Move the startup message to enable usage when trying SSL modes
vietj 1bb9d04
Fixed failing test due to bad db password policy
pendula95 e4cb4cf
Fixed incorrect assertions for SSL connection in TLS test
pendula95 05f18af
Added instructions for running external database with forced SSL conf…
pendula95 88e8209
The connection startup message should only be sent optionally, when c…
vietj 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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| #!/bin/bash | ||
|
|
||
| # force ssl | ||
| cp /tmp/pg_hba.conf /var/lib/postgresql/data/pg_hba.conf |
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,128 @@ | ||
| # 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. | ||
| # | ||
| # ---------------------- | ||
| # Authentication Records | ||
| # ---------------------- | ||
| # | ||
| # 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 a TCP/IP socket (encrypted or not) | ||
| # - "hostssl" is a TCP/IP socket that is SSL-encrypted | ||
| # - "hostnossl" is a TCP/IP socket that is not SSL-encrypted | ||
| # - "hostgssenc" is a TCP/IP socket that is GSSAPI-encrypted | ||
| # - "hostnogssenc" is a TCP/IP socket that is not GSSAPI-encrypted | ||
| # | ||
| # DATABASE can be "all", "sameuser", "samerole", "replication", a | ||
| # database name, a regular expression (if it starts with a slash (/)) | ||
| # 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 "+", a | ||
| # regular expression (if it starts with a slash (/)) 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. | ||
| # | ||
| # --------------- | ||
| # Include Records | ||
| # --------------- | ||
| # | ||
| # This file allows the inclusion of external files or directories holding | ||
| # more records, using the following keywords: | ||
| # | ||
| # include FILE | ||
| # include_if_exists FILE | ||
| # include_dir DIRECTORY | ||
| # | ||
| # FILE is the file name to include, and DIR is the directory name containing | ||
| # the file(s) to include. Any file in a directory will be loaded if suffixed | ||
| # with ".conf". The files of a directory are ordered by name. | ||
| # include_if_exists ignores missing files. FILE and DIRECTORY can be | ||
| # specified as a relative or an absolute path, and can be double-quoted if | ||
| # they contain spaces. | ||
| # | ||
| # ------------- | ||
| # Miscellaneous | ||
| # ------------- | ||
| # | ||
| # 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. | ||
|
|
||
| # CAUTION: Configuring the system for local "trust" authentication | ||
| # allows any local user to connect as any PostgreSQL user, including | ||
| # the database superuser. If you do not trust all your local users, | ||
| # use another authentication method. | ||
|
|
||
|
|
||
| # TYPE DATABASE USER ADDRESS METHOD | ||
|
|
||
| # "local" is for Unix domain socket connections only | ||
| local all all trust | ||
| # IPv4 local connections: | ||
| hostssl all all 127.0.0.1/32 trust | ||
| # IPv6 local connections: | ||
| hostssl all all ::1/128 trust | ||
| # Allow replication connections from localhost, by a user with the | ||
| # replication privilege. | ||
| local replication all trust | ||
| host replication all 127.0.0.1/32 trust | ||
| host replication all ::1/128 trust | ||
|
|
||
| hostssl all all all md5 |
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.
Uh oh!
There was an error while loading. Please reload this page.