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

Bug: Missing Aggressive Mode in GUI #228

Open
jobs-git opened this issue Jun 11, 2024 · 1 comment
Open

Bug: Missing Aggressive Mode in GUI #228

jobs-git opened this issue Jun 11, 2024 · 1 comment
Assignees

Comments

@jobs-git
Copy link

As the title says

@dkosovic dkosovic self-assigned this Jun 12, 2024
@dkosovic
Copy link
Member

I thought Aggressive Mode is mainly recommended for use with XAUTH and not with PSK to avoid offline brute force attack of the PSK, which isn't an issue with Main Mode as it doesn't leak the ID in clear text.

Extract from:

  • https://libreswan.org/man/ipsec.secrets.5.html

An additional complexity arises in the case of authentication by preshared secret in IKEv1 Main Mode: the responder will need to look up the secret before the Peer's ID payload has been decoded, so the ID used will be the IP address. IKEv1 Aggressive Mode (aggrmode=yes) can be used to work around this, at the price of leaking the ID in the clear and allowing a brute force attack against the PSK to be performed offline. PSKs are the least secure authentication method and should be avoided.

As the Windows built-in L2TP VPN client doesn't use Aggressive Mode, would there be many L2TP servers that use Aggressive Mode, or IPsec IKEv1 servers that use Aggressive mode but don't use XAUTH?

The NetworkManager-vpnc and NetworkManager-libreswan VPN clients I believe use Aggressive Mode with XAUTH (or in the NetworkManager-libreswan case just for IKEv1 and not IKEv2).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants