StrongSwan deploy hook: swanctl support #6094
Merged
Conversation
This file contains 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
sergiustheblack
force-pushed
the
feature/swanctl
branch
2 times, most recently
from
6e7deab
to
c9fb85d
Compare
|
fix the format errors please |
sergiustheblack
force-pushed
the
feature/swanctl
branch
3 times, most recently
from
e758030
to
3521674
Compare
sergiustheblack
force-pushed
the
feature/swanctl
branch
from
3521674
to
9c25365
Compare
fixed, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
acme.sh should support modern StrongSwan's swanctl tool.
The issue is that both legacy ipsec tool and swanctl can co-exist on the machine. So deploy hook maintains both tools independently and sync certificates into each config dir if it exists.
Notable changes:
ipsec --confdiroption, so I have to search for typical conf dir location (tested on Debian 12, Arch Linux, Centos Stream, FreeBSD 14)