T5871: ipsec remote access VPN: specify "cacerts" for client auth (backport #2708) #3298
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.
Change Summary
For authentication methods that depend on validating a client certificate against a CA (e.g. EAP-TLS), we currently do not explicitly tell strongswan which CA to use. This PR specifies the
cacerts
option explicitly for every connection to ensure the connection only accepts certificates signed by its specific CA.Types of changes
Related Task(s)
Related PR(s)
N/A
Component(s) name
ipsec remote-access
Proposed changes
The configured CA certificate fro the connection is added to the swanctl.conf connection definition using the
cacerts
option.How to test
Example configuration:
Validate that
/etc/swanctl/swanctl.conf
specifiescacerts = <ca certificate name>_1.pem
underremote
.Smoketest result
Checklist:
This is an automatic backport of pull request #2708 done by [Mergify](https://mergify.com).