This bug was fixed in the package wpa - 2.1-0ubuntu1

---------------
wpa (2.1-0ubuntu1) trusty; urgency=medium

  * New upstream release (LP: #1099755)
  * debian/get-orig-source: update for new git repository for the current
    hostap/wpasupplicant versions.
  * Dropped patches due to being applied upstream and included in the current
    source tarball:
    - debian/patches/11_wpa_gui_ftbfs_gcc_4_7.patch
    - debian/patches/13_human_readable_signal.patch
    - debian/patches/git_deinit_p2p_context_on_mgmt_remove_ff1f9c8.patch
    - debian/patches/libnl3-includes.patch
  * debian/patches/git_accept_client_cert_from_server.patch: revert the commit:
    "OpenSSL: Do not accept SSL Client certificate for server", which breaks
    many AAA servers that include both client and server EKUs. Cherry-picked
    from hostap git commit b62d5b5.
 -- Mathieu Trudel-Lapierre <mathieu...@ubuntu.com>   Tue, 04 Mar 2014 16:13:24 
-0500

** Changed in: wpa (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1099755

Title:
  [FFE] Upgrade wpa_supplicant from 1.0 to 2.1

Status in “wpa” package in Ubuntu:
  Fix Released
Status in “wpa” package in Debian:
  New

Bug description:
  New releases of wpa_supplicant are available: 1.1 (released
  2012-11-06) and 2.0 (released 2013-01-12) and 2.1 (released
  2014-02-04).

  2.1 contains a number of bugfixes relevant to frequent disconnects
  some might be seeing on networks where there is a lot of roaming, some
  IBSS (ad-hoc) fixes, etc.

  http://lists.shmoo.com/pipermail/hostap/2014-February/029440.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1099755/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to