Skip to content

Conversation

@volyrique
Copy link
Contributor

Also, disable password-based authentication using the MD5 hash algorithm, since that functionality has been officially deprecated.

Fix: #8061

Also, disable password-based authentication using the MD5 hash
algorithm, since that functionality has been officially deprecated:

https://www.postgresql.org/docs/18/auth-password.html

Signed-off-by: Anton Kirilov <[email protected]>
@volyrique
Copy link
Contributor Author

As all toolset changes, this PR is going to fail the CI checks because it triggers tests with all implementations, especially the ones that are known to be broken based on the latest continuous benchmarking run and/or those that don't use PostgreSQL at all. We also have the issue with the test runners running out of disk space - refer to the PHP checks, for example. On the other hand, all C and Ruby tests succeed.

With all that said, some tests are expected to start failing due to the authentication changes. My reading of issue #8061 and especially what the TechEmpower team has said is that the breakage would be acceptable, given that framework authors have had 2 years and a half (since the issue has been opened) to update their code and that password-based authentication using the MD5 hash algorithm is now officially deprecated. Let me know if I am wrong.

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.

Should we drop md5 auth in PostgreSQL ? We are in 2023 !!!

1 participant