Permit customization of secure transport layer in DcmTLSSCU #59
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.
Today, DcmTLSSCU requires certificate and key files to enable TLS.
The Windows platform has its own certificate store, and exporting all
certificates to the filesystem may not be desireable. Instead, we want
to populate the OpenSSL certificate store in memory from the Windows
certificate store.
This change allow us to derive from DcmTLSSCU to customize how TLS
transport layers are created and configured before we leave it over
to the default DcmTLSSCU::initNetwork implementation.