Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ipsec: strongswan: pubkey auth trusted CAs #8402

Open
2 tasks done
reet- opened this issue Mar 5, 2025 · 0 comments
Open
2 tasks done

ipsec: strongswan: pubkey auth trusted CAs #8402

reet- opened this issue Mar 5, 2025 · 0 comments
Labels
support Community support

Comments

@reet-
Copy link

reet- commented Mar 5, 2025

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:

# swanctl --list-conns
...
  remote public key authentication:
    id: %any
    cacerts: C=de, O=example, CN=ca

Whereas a new connection config results in:

# 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.

@AdSchellevis AdSchellevis added the support Community support label Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Community support
Development

No branches or pull requests

2 participants