diff options
| author | Tobias Brunner <tobias@strongswan.org> | 2015-08-03 13:55:36 +0200 |
|---|---|---|
| committer | Tobias Brunner <tobias@strongswan.org> | 2015-08-17 14:04:19 +0200 |
| commit | 774c8c38471da95725e7dcad17fad6c7d1edb2ab (patch) | |
| tree | 109ad3f8380f1869b8128762fd5c793ce49b66ab /src/libcharon/encoding/payloads/proposal_substructure.c | |
| parent | 9322e5b398efcf0a6f3bf576ef4b4b12b5ae6528 (diff) | |
| download | strongswan-774c8c38471da95725e7dcad17fad6c7d1edb2ab.tar.bz2 strongswan-774c8c38471da95725e7dcad17fad6c7d1edb2ab.tar.xz | |
auth-cfg: Matching one CA should be enough, similar to peer certificates
Not sure if defining multiple CA constraints and enforcing _all_ of them,
i.e. the previous behavior, makes even sense. To ensure a very specific
chain it should be enough to define the last intermediate CA. On the
other hand, the ability to define multiple CAs could simplify configuration.
This can currently only be used with swanctl/VICI based configs as `rightca`
only takes a single DN.
Diffstat (limited to 'src/libcharon/encoding/payloads/proposal_substructure.c')
0 files changed, 0 insertions, 0 deletions