[MXS-2963] Option to allow SSL and non-SSL traffic on same listener port Created: 2020-04-13 Updated: 2022-09-08 Resolved: 2022-09-08 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | Oy5p aegh | Assignee: | Todd Stoffel (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Imagine you want to roll-out MaxScale in an old infrastructure, where it is not feasible to reconfigure client applications for this or that port. |
| Comments |
| Comment by markus makela [ 2020-04-14 ] |
|
If I recall correctly, the lack of both SSL and non-SSL support on a single port was a conscious decision done to avoid accidental use of non-SSL connections when SSL was wanted. In my mind this is still a better choice as it more secure and, as you said, one can easily have two listeners to the same service: one with TLS enabled and the other without it. |