You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# swanctl --list-conns
...
remote public key authentication: (nil)
I found no way to only allow roadwarriors under a specific CA to connect.
Describe the solution you like
For pubkey auth it should be possible to only allow one or more trusted CAs.
Describe alternatives you considered
Also specifying a wildcard match (e.g. C=de, O=example, CN=* in the Remote Authentication Id field does not work even though strongswan supports this. Furthermore the Id field does not allow whitespaces but they are common in certificates. Both C=de, O=example and O=my Project are rejected.
The text was updated successfully, but these errors were encountered:
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
I'm in the process of migrating an IPsec roadwarrior setup currently configured in the legacy tunnel settings to the new Connections interface.
Our current pubkey auth settings in the legacy tunnel settings for the remote looks like this:
Whereas a new connection config results in:
I found no way to only allow roadwarriors under a specific CA to connect.
Describe the solution you like
For pubkey auth it should be possible to only allow one or more trusted CAs.
Describe alternatives you considered
Also specifying a wildcard match (e.g.
C=de, O=example, CN=*
in the Remote Authentication Id field does not work even though strongswan supports this. Furthermore the Id field does not allow whitespaces but they are common in certificates. Both C=de, O=example and O=my Project are rejected.The text was updated successfully, but these errors were encountered: