On Thu, 2016-01-28 at 09:50 +0100, Toby wrote:
> Hi,
> due to a delay in the upgrade of our corporate radius servers, I
> temporarily need to deactivate TLSv1.2 in phase1 of WPA2/EAP-PEAP, to
> bypass a conflict with wpa_supplicant >=2.4. (known issue)
> In wpa_supplicant.conf this would require a
Hi,
due to a delay in the upgrade of our corporate radius servers, I
temporarily need to deactivate TLSv1.2 in phase1 of WPA2/EAP-PEAP, to
bypass a conflict with wpa_supplicant >=2.4. (known issue)
In wpa_supplicant.conf this would require a parameter
phase="tls_disable_tlsv1_2=0".
But this
On Tue, 2016-01-26 at 22:57 +0100, Matthias Berndt wrote:
> Hi,
>
> here's the patch to simplify blob handling.
merged: https://git.gnome.org/browse/network-manager-openvpn/commit/?id
=4a94aa814f26bad03e1277b1d0d978deadb129ae
Thank you!
Thomas
signature.asc
Description: This is a digitally
On Thu, 2016-01-28 at 17:58 +0100, Toby wrote:
> I fully understand that this specific TLS1.2 issue is temporary and
> doesn't
> need to be addressed specifically. But there are many more
> wpa_supplicant
> parameters not covered by the settings spec, and there might be even
> more
> in upcoming
I fully understand that this specific TLS1.2 issue is temporary and doesn't
need to be addressed specifically. But there are many more wpa_supplicant
parameters not covered by the settings spec, and there might be even more
in upcoming releases. NM will always lag behind to some extend.
Therefore,
