This bug report related to bug 1546872 and patch will fix both of them.
There are two cases when sha256 passwords are allowed:
1. Connection is encrypted with SSL (works both with client built with YaSSL and OpenSSL)
2. Client is built with OpenSSL and server is started with private-key-path/public-key-path specified
Both don't work currently.
The fix will:
1. Allow to build xtrabackup with SSL support (with choice of YaSSL or OpenSSL)
2. Link sha256 plugin
Changes need to be done in packaging:
1. Make sure RPM and DEB versions build xtrabackup with system OpenSSL
2. Build binary tarball with YaSSL (or provide several versions for different distros) -- to be decided
This bug report related to bug 1546872 and patch will fix both of them.
There are two cases when sha256 passwords are allowed:
1. Connection is encrypted with SSL (works both with client built with YaSSL and OpenSSL) key-path/ public- key-path specified
2. Client is built with OpenSSL and server is started with private-
Both don't work currently.
The fix will:
1. Allow to build xtrabackup with SSL support (with choice of YaSSL or OpenSSL)
2. Link sha256 plugin
Changes need to be done in packaging:
1. Make sure RPM and DEB versions build xtrabackup with system OpenSSL
2. Build binary tarball with YaSSL (or provide several versions for different distros) -- to be decided