The proposed package is available here:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/focal-strongswan-
bug-fixes
I performed the test above to check if both plugins are installed again
and also if the old conf files were removed:
[in the same container I was using to describe the Test
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/strongswan/+git/strongswan/+merge/384385
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878887
Title:
No
** Changed in: strongswan (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: strongswan (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: strongswan (Ubuntu Focal)
Importance: Undecided => High
** Changed in:
@Christian Re: rm_conffile, I don't think this is a config file issue
(or is this command also used to remove shared libs/plugins? If so, then
definitely make sure to remove old plugins). The config snippets in
strongswan.d/charon are actually not relevant for charon-nm by default
(charon-nm uses
@Christian the plan you presented looks good to me.
I'd like to take advantage of this discussion and ask @Tobias his
opinion about all the plugins that were removed since 18.04 (the list of
plugins is the same in 20.10 and 20.04):
libstrongswan-eap-aka-3gpp2.so
libstrongswan-eap-dynamic.so
Thanks Tobias to provide detailed reasoning on these plugins!
@Lucas - chances are that when dropping the old plugins I didn't
rm_conffile all of them :-/
You might want to look into these steps:
1. re-add eap-peap + eap-dynamic (we had both before)
2. send the same to Debian and pass Tobias
EAP-PEAP (Protected EAP) is one of those protocols that nobody wants to
use (there are nicer, more modern alternatives) but lots of people have
to because it's what Microsoft implements. It's often used in
combination with EAP-MSCHAPv2 to authenticate e.g. WiFi clients (the TLS
connection in
** Also affects: strongswan (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: strongswan (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
When the system is clear installed Network Manager uses eap-ttls with mschapv2
login/password authentication and there are no problems, but when the system is
upgraded from previous versions like 18.04 it tries peap by default and fails,
so you need manually configure strongswan.conf with
Hi Alex,
Could you please provide some insight about your use case? The EAP-PEAP
plugin was disabled in Debian and the Debian maintainer prefers to keep
the package simple and not enable too complicated stuff like EAP plugins
[1]. For us to convince them to accept its inclusion back we need some
I confirm the EAP-PEAP plugin is missing, check below.
Bionic:
$ dpkg -c libcharon-extra-plugins_5.6.2-1ubuntu2.5_amd64.deb | grep eap-peap
-rw-r--r-- root/root 777 2019-11-12 08:32
./etc/strongswan.d/charon/eap-peap.conf
-rw-r--r-- root/root 18616 2019-11-12 08:32
11 matches
Mail list logo
