Details
-
New Feature
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
Q2/2025 Development, Q3/2025 Maintenance
Description
In MySQL 5.6 and 5.7, you have the option of using the SHA256 password algorithm. The current method (mysql_native_password) leverages SHA1 and this has been proven to be no longer as secure as one would expect today.
Find out more here:
- http://mysqlblog.fivefarmers.com/2015/08/31/protecting-mysql-passwords-with-sha256_password-plugin/
- https://dev.mysql.com/doc/refman/5.7/en/sha256-authentication-plugin.html
UPDATE:
https://dev.mysql.com/doc/mysql-security-excerpt/8.0/en/sha256-pluggable-authentication.html
Attachments
Issue Links
- blocks
-
MDEV-37600 Backport MDEV-9804 "Implement a caching_sha2_password plugin" to MariaDB Community Server 11.4/11.8
-
- Closed
-
- causes
-
MDEV-37339 Errors about caching_sha2_password upon server startup with WolfSSL
-
- Closed
-
- is duplicated by
-
MDEV-36382 mariadb支持caching_sha2_password
-
- Closed
-
- is part of
-
MDEV-28906 MySQL 8.0 desired compatibility
-
- Open
-
- relates to
-
CONC-229 SHA256 authentication plugin
-
- Closed
-
-
CONJ-327 Handle sha256_password plugin
-
- Closed
-
-
CONJS-76 Implement sha256_password support
-
- Closed
-
-
CONJS-77 Implement caching_sha256_password support
-
- Closed
-
-
MDEV-12160 Modern alternative to the SHA1 authentication plugin
-
- Closed
-
-
MXS-1325 Add sha256_password authenticator
-
- Closed
-
-
MXS-4270 ed25519 authentication support
-
- Closed
-
-
ODBC-241 Add parameter that corresponds to MYSQL_SERVER_PUBLIC_KEY option from MariaDB Connector/C
-
- Closed
-
-
CONC-312 Implement caching_sha2_password plugin
-
- Closed
-
-
CONJ-663 Implement caching_sha2_password plugin
-
- Closed
-
-
MDEV-37554 MariaDB auth protocol differs from MySQL
-
- Confirmed
-