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
Should we drop md5 auth in PostgreSQL ? We are in 2023 !!! #8061
Comments
@joanhey How many frameworks are failing because of this? Do you know offhand and can ping the contributors here? |
It should be default to sasl auth at this point. But there are some points I consider worth to mention:
|
@fafhrd91 Maybe it worth to implement sasl auth in ntex postgres. |
I think that fail for the auth ~30 frameworks permutations. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the new PostgreSQL official docker image, we have again the problem with md5 auth.
I can fix it, but is it realistic to use md5 auth in 2023 ?
Some frameworks that fail, they had the time and energy to patch libpq for performance. So they can use some time to add the new scram (sha-256) auth in their frameworks.
More info: #7557 #8002
Give your feedback.
The text was updated successfully, but these errors were encountered: