From: Domagoj Stolfa <ds815@gmx.com>
To: 48626@debbugs.gnu.org
Subject: [bug#48626] [PATCH] strongswan: enable more sensible defaults.
Date: Mon, 24 May 2021 16:35:02 +0100 [thread overview]
Message-ID: <YKvHpny1wBT6pjja@pepehands> (raw)
[-- Attachment #1: Type: text/plain, Size: 2706 bytes --]
Presently, the strongswan defaults are too minimal to be used with most
common VPN setups. This commit enables support for a number of things
that should make strongswan much more usable in Guix. It also explicitly
disables AESNI in order to not rely on an Intel implementation.
---
gnu/packages/networking.scm | 52 +++++++++++++++++++++++++++++++++++--
1 file changed, 50 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/networking.scm b/gnu/packages/networking.scm
index 8bcaa98fbb..1ce7adfde9 100644
--- a/gnu/packages/networking.scm
+++ b/gnu/packages/networking.scm
@@ -2863,14 +2863,62 @@ displays the results in real time.")
(list
;; Disable bsd-4 licensed plugins.
"--disable-des"
- "--disable-blowfish")))
+ "--disable-blowfish"
+ ;; Disable AESNI
+ "--disable-aesni"
+ ;; Disable systemd
+ "--disable-systemd"
+ ;; Don't use mysql or OpenLDAP
+ "--disable-mysql"
+ "--disable-ldap"
+ ;; Enable the rest needed for a sensible configuration
+ "--enable-attr-sql"
+ "--enable-chapoly"
+ "--enable-curl"
+ "--enable-dhcp"
+ "--enable-farp"
+ "--enable-md4"
+ "--enable-eap-aka"
+ "--enable-eap-aka-3gpp"
+ "--enable-eap-dynamic"
+ "--enable-eap-identity"
+ "--enable-eap-md5"
+ "--enable-eap-mschapv2"
+ "--enable-eap-peap"
+ "--enable-eap-radius"
+ "--enable-eap-sim"
+ "--enable-eap-sim-file"
+ "--enable-eap-simaka-pseudonym"
+ "--enable-eap-simaka-reauth"
+ "--enable-eap-simaka-sql"
+ "--enable-eap-tls"
+ "--enable-eap-tnc"
+ "--enable-eap-ttls"
+ "--enable-xauth-eap"
+ "--enable-ext-auth"
+ "--enable-led"
+ "--enable-ha"
+ "--enable-mediation"
+ "--enable-soup"
+ "--enable-sql"
+ "--enable-sqlite"
+ "--enable-openssl"
+ "--enable-xauth-eap"
+ "--enable-xauth-noauth"
+ "--enable-xauth-pam"
+ ;; Use libcap by default
+ "--with-capabilities=libcap")))
(inputs
`(("curl" ,curl)
("gmp" ,gmp)
("libgcrypt" ,libgcrypt)
- ("openssl" ,openssl)))
+ ("openssl" ,openssl)
+ ("libsoup" ,libsoup)
+ ("libcap" ,libcap)
+ ("linux-pam" ,linux-pam)))
(native-inputs
`(("coreutils" ,coreutils)
+ ("pkg-config" ,pkg-config)
("tzdata" ,tzdata-for-tests)))
(synopsis "IKEv1/v2 keying daemon")
(description "StrongSwan is an IPsec implementation originally based upon
--
2.31.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-05-24 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 15:35 Domagoj Stolfa [this message]
2021-05-24 20:11 ` [bug#48626] [PATCH] strongswan: enable more sensible defaults Domagoj Stolfa
2021-06-06 13:44 ` bug#48626: " Tobias Geerinckx-Rice via Guix-patches via
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YKvHpny1wBT6pjja@pepehands \
--to=ds815@gmx.com \
--cc=48626@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).