brew

strongswan mit Homebrew, apk, apt, dnf, Nix, pacman, zypper installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für strongswan in AI-Agent-Workflows.

Installationsbefehl Sicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install strongswan

local Homebrew formula metadata

Linux

Alpine Linux apkverifiziert · 92%

sudo apk add strongswan

Alpine Linux edge package indexes · strongswan · Quelle: dl-cdn.alpinelinux.org

Debian aptverifiziert · 92%

sudo apt install strongswan

Debian stable package indexes · strongswan · Quelle: deb.debian.org

Fedora dnfverifiziert · 92%

sudo dnf install strongswan

Fedora Rawhide package metadata · strongswan · Quelle: dl.fedoraproject.org

Nixverifiziert · 92%

nix profile install nixpkgs#strongswan

nixpkgs package indexes · pkgs/by-name/st/strongswan/package.nix · Quelle: api.github.com

Arch Linux pacmanverifiziert · 92%

sudo pacman -S strongswan

Arch Linux sync databases · strongswan · Quelle: geo.mirror.pkgbuild.com

openSUSE zypperverifiziert · 92%

sudo zypper install strongswan

openSUSE Tumbleweed package metadata · strongswan · Quelle: download.opensuse.org

Überblick

Paketzusammenfassung

VPN based on IPsec

Projektlinks

Befehle und Aliase

charon-cmd
ipsec
pki
swanctl

Verlauf

Projektgeschichte und Nutzung

strongSwan is a long-running open source IPsec and IKE implementation used to build policy- and route-based VPNs. In package-manager culture it is a substantial security package: a suite of daemons, plugins, and command-line tools such as `ipsec`, `swanctl`, `pki`, and `charon-cmd` rather than a single small executable.

Projektgeschichte

The official strongSwan history says the project launched in 2005 as a fork of the discontinued FreeS/WAN project, integrating the X.509 patch its authors had contributed since 2000. The project later replaced inherited FreeS/WAN code with a new modular IKE daemon written in a modern object-oriented C style.

strongSwan initially used the new daemon for IKEv2 while IKEv1 remained handled by an extended FreeS/WAN pluto daemon. Because IKEv2 adoption by other vendors was slower than expected, strongSwan added IKEv1 support to the new daemon in strongSwan 5.0 in 2012 and removed pluto and other legacy components.

Adoptionsgeschichte

The project documents more than 400,000 lines of code, more than 400 automated tests, and more than 110 contributors on its official about page. The input package facts show broad packaging across Homebrew, Debian and Ubuntu components, Fedora, Nix, pacman, APK, and zypper, reflecting its role as infrastructure software rather than a niche CLI.

Wie es verwendet wird

Administrators use strongSwan to configure, control, and monitor IPsec/IKE VPNs. Official documentation describes `swanctl` as the command-line utility for configuring, controlling, and monitoring the IKE charon daemon through the vici interface, while the broader documentation covers configuration files, certificates, kernel integration, and platform-specific builds.

Warum Paket-Nerds sich dafür interessieren

Package nerds care about strongSwan because it sits at the intersection of kernel networking, cryptography, service management, plugin selection, and distro policy. Packaging it correctly means handling default configuration paths, private-key directories, optional plugins, service startup, and compatibility across Linux, macOS, FreeBSD, Android, and other supported environments.

Zeitleiste

2000: strongSwan authors were contributing an X.509 patch to FreeS/WAN.
2005: strongSwan launched as a fork of the discontinued FreeS/WAN project.
2012: strongSwan 5.0 added IKEv1 support to the new daemon and removed pluto and other legacy components.
2022: secunet Security Networks AG acquired intellectual property rights to the strongSwan project.

Related projects

FreeS/WAN is the direct ancestor named by the official project history. The official documentation also positions `swanctl`, `charon`, `pki`, and the vici interface as core parts of the modern strongSwan toolchain.

Quellen

https://docs.strongswan.org/docs/latest/devs/devs.html
https://docs.strongswan.org/docs/latest/swanctl/swanctl.html
https://strongswan.org/about.html
source_facts.package-manager

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

narrow executable package without higher-risk signals

Signale

metadata:no-higher-risk-signals

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
Installiert mit 1 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: /etc/strongswan.conf/etc/strongswan.d//etc/swanctl/swanctl.conf/etc/swanctl/conf.d/*.conf

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix: /etc/swanctl/private//etc/swanctl/rsa//etc/swanctl/ecdsa//etc/swanctl/pkcs8//etc/swanctl/pkcs12//etc/swanctl/swanctl.conf

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit
`charon-cmd`	cli	globales Executable
`ipsec`	cli	globales Executable
`pki`	cli	globales Executable
`swanctl`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25

Manager-Version6.0.7

Manager aktualisiert2026-06-08

lokale DatenOK

Upstreamnot checked

neueste erkannte Versionnicht erkannt

https://www.strongswan.org

InfoRelease/tag comparison is only available for GitHub repositories.https://www.strongswan.orgnone Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:strongswan
Version	6.0.7
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/strongswan
Homepage	https://www.strongswan.org
Repository	https://github.com/strongswan/strongswan
Upstream-Dokumentation	https://docs.strongswan.org/
Lizenz	GPL-2.0-or-later
Quellarchiv	https://download.strongswan.org/strongswan-6.0.7.tar.bz2
Zuletzt aktualisiert	2026-06-08T08:40:44Z
Pulse	updated
Abhängigkeiten	openssl@3
Von macOS bereitgestellte Bibliotheken	curl
Bottle	verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert
Einschränkungen	You will have to run both "ipsec" and "charon-cmd" with "sudo".

Registry-Fakten

Details aus der Quelldatenbank

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	strongswan
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Debian apt95%

charon-cmd 6.0.1-6+deb13u5

standalone IPsec client