[MXS-4865] 5.5.5- prefix should not be added if all backends are MariaDB 11 Created: 2023-11-16  Updated: 2024-01-22  Resolved: 2023-12-27

Status: Closed
Project: MariaDB MaxScale
Component/s: Protocol
Affects Version/s: None
Fix Version/s: 6.4.14, 22.08.12, 23.02.9, 23.08.5

Type: Bug Priority: Major
Reporter: Richard Stracke Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-28910 remove the 5.5.5- version hack Closed
relates to MXS-2232 version_string prefix 5.5.5- is alway... Closed
relates to MXS-2890 5.5.5 prefix is always added even wit... Closed
Sprint: MXS-SPRINT-198

 Description   

Due the fact, that 5.5.5. hack will be removed in MariaDB 11 (MDEV-28910)
the same should be possible with Maxscale.

Some applications like the security scanner telstra detects MariaDB as
version MariaDB 5.5.5 and throw Security false alarms for MySQL 5.5.5,
which are fixed since many years,
so avoiding adding 5.5.5 must be an optional possible option.

 Comments   
Comment by markus makela [ 2023-12-04 ]

So the desired behavior is to not send the 5.5.5- prefix when configured with a version string of 11.0 or higher?

Comment by markus makela [ 2023-12-21 ]

MaxScale now follows the same behavior that MariaDB does and only appends the 5.5.5 prefix for MariaDB 10 version strings.

Comment by Richard Stracke [ 2023-12-27 ]

There should be a possibility to remove the version string,
Server have the possibility to set. a fake version to override the addition of
"5.5.5." prefix.
Maxscales "version_string" not work in the same way.
So the request is to esablish a method to avoid the addition of the fake 5.5.5 in some way.

Comment by markus makela [ 2023-12-27 ]

I'll still close this as Fixed as the version_string can now be set to MariaDB 11 after which the 5.5.5- prefix is not added.

Generated at Thu Feb 08 04:31:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.