| 1 |
wpasupplicant (2:2.6-19) unstable; urgency=medium |
| 2 |
|
| 3 |
With this release, wpasupplicant no longer respects the system |
| 4 |
default minimum TLS version, defaulting to TLSv1.0, not TLSv1.2. If |
| 5 |
you're sure you will never connect to EAP networks requiring anything less |
| 6 |
than 1.2, add this to your wpasupplicant configuration: |
| 7 |
|
| 8 |
tls_disable_tlsv1_0=1 |
| 9 |
tls_disable_tlsv1_1=1 |
| 10 |
|
| 11 |
wpasupplicant also defaults to a security level 1, instead of the system |
| 12 |
default 2. Should you need to change that, change this setting in your |
| 13 |
wpasupplicant configuration: |
| 14 |
|
| 15 |
openssl_ciphers=DEFAULT@SECLEVEL=2 |
| 16 |
|
| 17 |
Unlike wpasupplicant, hostapd still respects system defaults. |
| 18 |
|
| 19 |
-- Andrej Shadura <[email protected]> Sat, 15 Dec 2018 14:22:18 +0100 |
| 20 |
|
| 21 |
wpasupplicant (0.6.2-1) unstable; urgency=low |
| 22 |
|
| 23 |
The -w (wait for network interface to exist) command line option no longer |
| 24 |
exists. If you have scripts that require this option, it is time to change |
| 25 |
them, or use one of the two supported modes of operation explained at |
| 26 |
/usr/share/doc/wpasupplicant/README.modes.gz. |
| 27 |
|
| 28 |
ifupdown supports hot-plugged network devices via the "allow-hotplug" class |
| 29 |
of operation. An example /etc/network/interfaces configuration stanza would |
| 30 |
look like: |
| 31 |
|
| 32 |
allow-hotplug wlan0 |
| 33 |
iface wlan0 inet dhcp |
| 34 |
wpa-ssid myssid |
| 35 |
wpa-psk mysecretpassphrase |
| 36 |
|
| 37 |
network-manager is also able to handle hot-plugged network devices. |
| 38 |
|
| 39 |
-- Kel Modderman <[email protected]> Mon, 14 Jan 2008 18:02:17 +1000 |