Repository navigation
Conversation
ttc0419
force-pushed
the
strongswan-6.1.0
branch
from
October 16, 2026 13:51
f01653c to
120519d
Compare
Member
|
I'm not yet sure whether we should stop offering IKEv1. There are still some configurations that use it. That’s why I recently added a warning in LuCI noting that IKEv1 is deprecated and will be removed soon. As long as stronswan still supports IKEv1, I’d like to continue offering it. I’d prefer to also add a warning to the init script prompting users to upgrade. I'm more in favor of disabling stroke and relying entirely on vici (swanctl). |
Remove the blowfish, duplicheck, gcrypt, led and smp plugins, which upstream removed in 6.1.0 and recommends disabling in older releases. Drop their package definitions, full-package dependencies and version test entries, along with the duplicheck installation rule. Link: https://www.strongswan.org/blog/2026/09/07/strongswan-6.1.0-released.html Signed-off-by: Tianchen Tang <ttc0419@outlook.com>
ttc0419
force-pushed
the
strongswan-6.1.0
branch
from
October 16, 2026 16:36
120519d to
b173dea
Compare
Update to 6.1.0, which fixes eleven vulnerabilities. Explicitly enable IKEv1 to preserve support now that upstream disables it by default. Refresh the gmpdh patch, drop the wolfSSL header patch already included upstream and remove the obsolete libfast configure option. Link: https://www.strongswan.org/blog/2026/09/07/strongswan-6.1.0-released.html Signed-off-by: Tianchen Tang <ttc0419@outlook.com>
ttc0419
force-pushed
the
strongswan-6.1.0
branch
from
October 16, 2026 16:40
b173dea to
3ac57bf
Compare
Drop the stroke plugin and the strongswan-ipsec package, including the starter-based init script and ipsec.conf/ipsec.secrets installation. Use swanctl in the ISAKMP and minimal meta-packages while retaining IKEv1 support. Move ipsec.user installation and conffile tracking to the updown plugin so its hotplug hook remains usable without the legacy ipsec package. Remove the obsolete version tests. Link: https://strongswan.org/blog/2024/12/03/strongswan-6.0.0-released.html Signed-off-by: Tianchen Tang <ttc0419@outlook.com>
ttc0419
force-pushed
the
strongswan-6.1.0
branch
from
October 16, 2026 16:42
3ac57bf to
e66a740
Compare
Author
|
@feckert restored ikev1 support and added a commit to drop stoke backend |
openwrt-ai
reviewed
Oct 17, 2026
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📦 Package Details
Maintainer: @BKPepe @feckert @Thermi @pprindeville
Description:
Release notes:
https://www.strongswan.org/blog/2026/09/07/strongswan-6.1.0-released.html
Closes: #30738
🧪 Run Testing Details
✅ Formalities
If your PR contains a patch:
git am(e.g., subject line, commit description, etc.)
We must try to upstream patches to reduce maintenance burden.