[MDEV-30402] Encrypted mariabackup SST breaks on distributions with newer socat v1.7.4.x Created: 2023-01-13 Updated: 2023-06-21 Resolved: 2023-04-13 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera SST, SSL |
| Affects Version/s: | 10.4.27, 10.5.18, 10.6.11, 10.7.7, 10.8.6, 10.9.4, 10.10.2, 10.11.1 |
| Fix Version/s: | 11.1.1, 10.11.3, 10.4.29, 10.5.20, 10.6.13, 10.8.8, 10.9.6, 10.10.4 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Hartmut Holzgraefe | Assignee: | Julius Goryavsky |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Environment: |
Ubuntu 22.04, RHEL 8.7, or any other distribution that comes with socat version >= 1.7.4.0 |
||
| Description |
|
socat version 1.7.4.0 has added this new feature:
This leads to setups using encrypted mariabackup SST method with encrypt=4 (haven't tested other encryption modes yet) to fail with
on the donor side on distributions that have already upgraded to the new socat version, e.g. RHEL 8 and Ubuntu 22.04 "Jammy" which both come with 1.7.4.1 For now I have been able to fix this by adding the new no-sni=1 option to the donor side socat call when detecting socat version 1.7.4+, but I don't understand the situation well enough yet to say whether this may not be a bit too brute force after all ...
|
| Comments |
| Comment by Julius Goryavsky [ 2023-04-13 ] |
|
Fixed, https://github.com/MariaDB/server/commit/d1a4315f4cb096c2fd81c96bc4afc6bb618bae49 |