From: dstolfa <dstolfa@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Enable MSCHAPv2 with StrongSwan.
Date: Mon, 03 May 2021 16:24:44 +0200 [thread overview]
Message-ID: <20210503142444.-hAJB_b2SJTxmKoNzCgGzSkVigxYBt4SOcSLFiZg5JI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30642@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]
There is an updated pull request by dstolfa against master on the void-packages repository
https://github.com/dstolfa/void-packages master
https://github.com/void-linux/void-packages/pull/30642
Enable MSCHAPv2 with StrongSwan.
StrongSwan on Void currently has issues with EAP-MSCHAPv2 in different ways.
(1) eap-identity needs to be enabled in order for config files with `eap_identity=%any` and similar lines to work (you essentially end up with `EAP_NAK` when `EAP_IDENTITY` is requested);
(2) eap-mschapv2 requires `md4` to be enabled as a plugin
(3) eap-dynamic **might** be required on some setups, so this pull request enables it to avoid issues in the future.
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (ARCH-LIBC)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] aarch64-musl
- [x] armv7l
- [x] armv6l-musl
I have **not tested** if it runs on any of the cross builds, I simply tested that it indeed does build.
A patch file from https://github.com/void-linux/void-packages/pull/30642.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-30642.patch --]
[-- Type: text/x-diff, Size: 1379 bytes --]
From d7cb895d4566bfcd4446bfa51ebcd0e1f5c30b3f Mon Sep 17 00:00:00 2001
From: Domagoj Stolfa <ds815@gmx.com>
Date: Mon, 3 May 2021 15:10:25 +0100
Subject: [PATCH] strongswan: enable options that are required for MSCHAPv2.
---
srcpkgs/strongswan/template | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/strongswan/template b/srcpkgs/strongswan/template
index f0be1ff9bdc3..36abce68ea26 100644
--- a/srcpkgs/strongswan/template
+++ b/srcpkgs/strongswan/template
@@ -1,13 +1,12 @@
# Template file for 'strongswan'
pkgname=strongswan
version=5.8.4
-revision=1
+revision=2
build_style=gnu-configure
# tpm support waits on libtss2
-configure_args="--disable-static --enable-blowfish --enable-curl
- --enable-eap-radius --enable-eap-mschapv2 --enable-eap-md5 --enable-led
- --enable-ha --enable-dhcp --enable-mediation --enable-soup --disable-des
- --enable-chapoly --enable-nm"
+configure_args="--disable-static --enable-blowfish --enable-curl --enable-md4
+ --enable-eap-radius --enable-eap-mschapv2 --enable-eap-md5 --enable-eap-identity --enable-eap-dynamic
+ --enable-led --enable-ha --enable-dhcp --enable-mediation --enable-soup --enable-chapoly --enable-nm"
hostmakedepends="pkg-config flex bison python"
makedepends="gmp-devel libsoup-devel libldns-devel unbound-devel libcurl-devel NetworkManager-devel"
depends="iproute2 sqlite"
next prev parent reply other threads:[~2021-05-03 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 14:21 [PR PATCH] " dstolfa
2021-05-03 14:24 ` dstolfa [this message]
2021-05-03 14:39 ` [PR PATCH] [Updated] " dstolfa
2021-05-03 15:23 ` [PR PATCH] [Merged]: " ericonr
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210503142444.-hAJB_b2SJTxmKoNzCgGzSkVigxYBt4SOcSLFiZg5JI@z \
--to=dstolfa@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).