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. All CAs configured for any remote access VPN configuration are loaded into strongswan so one remote access configuration will accept a client certificate signed by the CA configured on another connection.
Description
Description
Details
Details
- Version
- -
- Is it a breaking change?
- Perfectly compatible
Related Objects
Related Objects
- Mentioned In
- rVYOSONEX55ae2ca0b17f: op-mode: ipsec: T6407: fix profile generation
rVYOSONEXe6fe6e50a5c8: op-mode: ipsec: T6407: fix profile generation
rVYOSONEX28983d57e6d1: Merge pull request #3298 from vyos/mergify/bp/sagitta/pr-2708
rVYOSONEX7100a5797bce: T5871: ipsec remote access VPN: specify "cacerts" for client auth.
rVYOSONEXecc83562b4d7: T5871: ipsec remote access VPN: specify "cacerts" for client auth.
rVYOSONEX041a57d69dc7: Merge pull request #2708 from lucasec/t5871
rVYOSONEX010c5890c9bd: Merge pull request #3205 from vyos/mergify/bp/sagitta/pr-3202
rVYOSONEX557694e1ab61: ipsec: T5606: T5871: Use multi node for CA certificates
rVYOSONEX952b1656f516: ipsec: T5606: T5871: Use multi node for CA certificates
rVYOSONEXd15db95d96ea: Merge pull request #3202 from sarthurdev/T5606_1