feat: default Postgres SSL protocol version to TLSv1.3 #3408
Conversation
This file contains 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
gbartolini
requested review from
fcanovai,
leonardoce,
mnencia,
phisco,
sxd and
armru
as code owners
github-actions
bot
added
backport-requested ◀️
|
❗ By default, the pull request is configured to backport to all release branches.
|
gbartolini
changed the title
gbartolini
changed the title
4 tasks
armru
approved these changes
Nov 24, 2023
litaocdl
approved these changes
Nov 27, 2023
Previously, CloudNativePG lacked the capability for users to configure specific TLS settings, relying on the default settings of PostgreSQL. To address security and compliance concerns, CloudNativePG now sets the `ssl_min_protocol_version` and `ssl_max_protocol_version` GUCs to TLSv1.3 by default. Additionally, users now have the flexibility to override these default options, along with the `ssl_ciphers` configuration. Closes #3407 Closes #3376 Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
|
/test depth=push test_level=4 feature_type=service-connectivity,replication |
|
@sxd, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/7010018465 |
|
@sxd, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/7010087146 |
Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
|
/test depth=push test_level=4 feature_type=service-connectivity,replication |
|
@sxd, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/7013922432 |
|
/test test_level=4 feature_type=service-connectivity,replication |
|
@sxd, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/7013973399 |
… pg11 Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
sxd
approved these changes
Nov 28, 2023
cnpg-bot
pushed a commit
that referenced
this pull request
Nov 28, 2023
Previously, CloudNativePG lacked the capability for users to configure specific TLS settings, relying on the default settings of PostgreSQL. To address security and compliance concerns, CloudNativePG now sets the `ssl_min_protocol_version` and `ssl_max_protocol_version` GUCs to TLSv1.3 by default. This default settings is only for Postgres >= 12, since version 11 doesn't have support for these GUCs Additionally, users now have the flexibility to override these default options, along with the `ssl_ciphers` configuration. Closes #3407 Closes #3376 Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com> Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com> Co-authored-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com> (cherry picked from commit 38ce92e)
cnpg-bot
pushed a commit
that referenced
this pull request
Nov 28, 2023
Previously, CloudNativePG lacked the capability for users to configure specific TLS settings, relying on the default settings of PostgreSQL. To address security and compliance concerns, CloudNativePG now sets the `ssl_min_protocol_version` and `ssl_max_protocol_version` GUCs to TLSv1.3 by default. This default settings is only for Postgres >= 12, since version 11 doesn't have support for these GUCs Additionally, users now have the flexibility to override these default options, along with the `ssl_ciphers` configuration. Closes #3407 Closes #3376 Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com> Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com> Co-authored-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com> (cherry picked from commit 38ce92e)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, CloudNativePG lacked the capability for users to configure specific TLS settings, relying on the default settings of PostgreSQL.
To address security and compliance concerns, CloudNativePG now sets the
ssl_min_protocol_versionandssl_max_protocol_versionGUCs to TLSv1.3 by default.Additionally, users now have the flexibility to override these default options, along with the
ssl_ciphersconfiguration.Closes #3407
Closes #3376