Add SSL connection options to MariaDB #331
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request enables SSL network connectivity for MariaDB. .pem files should already be created and available in a readable directory and the MariaDB server enabled for SSL.
Options allow one-way or two-way SSL to be selected.
If SSL is successfully enabled the SSL cipher is reported. Where SSL is not enabled an empty string {} is reported.
Where SSL filenames are given the names are concatenated to the CApath and passed directly for each individual file. If all filenames are empty then the CApath option will be passed instead with the directory name.
The default SSL Cipher is listed as "server" meaning use the server default. This value can be changed to another available cipher.
Note: the SSL Cipher requires an update to the mariatcl library and will only work from HammerDB v4.5 unless built from source.
The same SSL options also available in the CLI.