-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Modify default cipher suite for IKEv2 #981
Comments
In addition to these changes, changes in the resulting iOS profile will be required: Current:
Change to:
|
On iOS it runs great! But on Windows 10 I get the following message when trying to activate the VPN: I'm running Windows 10 Pro version 1803 build 17134.48 |
Could anybody provide some debug information from windows 10, please? |
I still have the profile installed on this machine, I just don't know where to look. |
For some reason that's happening because of switching from ECP256 to ECP384 |
I forgot to switch the ec params. Should work now. ping @pguizeline |
Hi Jack! The VPN now works on Windows 10 with the latest changes. I've tested:
The iOS seems to be unable to connect, I'm using the latest 11.4 I can test macOS later today. Thanks for all your help! |
As of August 2015, NSA recommends a stronger set of algorithms than the ones we currently configure. These changes were made to provide improved resistance to theoretical attacks from quantum computers.
The current cipher suite is:
The new proposed cipher suite is:
The primary changes are that:
More information about available cipher suites for IKEv2 is available in the StrongSwan documentation.
The text was updated successfully, but these errors were encountered: