Log message:
Pullup ticket #5578 - requested by maya
net/wpa_supplicant: security patch

Revisions pulled up:
- net/wpa_supplicant/Makefile                                   1.18
- net/wpa_supplicant/distinfo                                   1.10
- net/wpa_supplicant/patches/patch-src_ap_ieee802__11.c         1.1
- net/wpa_supplicant/patches/patch-src_ap_wpa__auth.c           1.1
- net/wpa_supplicant/patches/patch-src_ap_wpa__auth.h           1.1
- net/wpa_supplicant/patches/patch-src_ap_wpa__auth__ft.c       1.1
- net/wpa_supplicant/patches/patch-src_ap_wpa__auth__i.h        1.1
- net/wpa_supplicant/patches/patch-src_common_wpa__common.h     1.1
- net/wpa_supplicant/patches/patch-src_rsn__supp_tdls.c         1.1
- net/wpa_supplicant/patches/patch-src_rsn__supp_wpa.c          1.1
- net/wpa_supplicant/patches/patch-src_rsn__supp_wpa__ft.c      1.1
- net/wpa_supplicant/patches/patch-src_rsn__supp_wpa__i.h       1.1
- net/wpa_supplicant/patches/patch-wpa__supplicant_wnm__sta.c   1.1

-------------------------------------------------------------------
   Module Name:    pkgsrc
   Committed By:   maya
   Date:           Mon Oct 16 10:26:21 UTC 2017

   Modified Files:
           pkgsrc/net/wpa_supplicant: Makefile distinfo
   Added Files:
           pkgsrc/net/wpa_supplicant/patches: patch-src_ap_ieee802__11.c
               patch-src_ap_wpa__auth.c patch-src_ap_wpa__auth.h
               patch-src_ap_wpa__auth__ft.c patch-src_ap_wpa__auth__i.h
               patch-src_common_wpa__common.h patch-src_rsn__supp_tdls.c
               patch-src_rsn__supp_wpa.c patch-src_rsn__supp_wpa__ft.c
               patch-src_rsn__supp_wpa__i.h patch-wpa__supplicant_wnm__sta.c

   Log message:
   wpa_supplicant: apply upstream patch for security advisory

   Patches from Juoni Malinen and Mathy Vanhoef.

   Fixes:
   - CVE-2017-13077
   - CVE-2017-13078
   - CVE-2017-13079
   - CVE-2017-13080
   - CVE-2017-13081
   - CVE-2017-13082
   - CVE-2017-13086
   - CVE-2017-13087
   - CVE-2017-13088

   Tested by leot, thanks!

   Subject: [PATCH 1/8] hostapd: Avoid key reinstallation in FT handshake

   Do not reinstall TK to the driver during Reassociation Response frame
   processing if the first attempt of setting the TK succeeded. This avoids
   issues related to clearing the TX/RX PN that could result in reusing
   same PN values for transmitted frames (e.g., due to CCM nonce reuse and
   also hitting replay protection on the receiver) and accepting replayed
   frames on RX side.

   This issue was introduced by the commit
   0e84c25434e6a1f283c7b4e62e483729085b78d2 ('FT: Fix PTK configuration in
   authenticator') which allowed wpa_ft_install_ptk() to be called multiple
   times with the same PTK. While the second configuration attempt is
   needed with some drivers, it must be done only if the first attempt
   failed.

   Subject: [PATCH 2/8] Prevent reinstallation of an already in-use group key

   Track the current GTK and IGTK that is in use and when receiving a
   (possibly retransmitted) Group Message 1 or WNM-Sleep Mode Response, do
   not install the given key if it is already in use. This prevents an
   attacker from trying to trick the client into resetting or lowering the
   sequence counter associated to the group key.

   Subject: [PATCH 3/8] Extend protection of GTK/IGTK reinstallation of WNM-Sleep
    Mode cases

   This extends the protection to track last configured GTK/IGTK value
   separately from EAPOL-Key frames and WNM-Sleep Mode frames to cover a
   corner case where these two different mechanisms may get used when the
   GTK/IGTK has changed and tracking a single value is not sufficient to
   detect a possible key reconfiguration.

   Subject: [PATCH 4/8] Prevent installation of an all-zero TK

   Properly track whether a PTK has already been installed to the driver
   and the TK part cleared from memory. This prevents an attacker from
   trying to trick the client into installing an all-zero TK.

   This fixes the earlier fix in commit
   ad00d64e7d8827b3cebd665a0ceb08adabf15e1e ('Fix TK configuration to the
   driver in EAPOL-Key 3/4 retry case') which did not take into account
   possibility of an extra message 1/4 showing up between retries of
   message 3/4.

   Subject: [PATCH 5/8] Fix PTK rekeying to generate a new ANonce

   The Authenticator state machine path for PTK rekeying ended up bypassing
   the AUTHENTICATION2 state where a new ANonce is generated when going
   directly to the PTKSTART state since there is no need to try to
   determine the PMK again in such a case. This is far from ideal since the
   new PTK would depend on a new nonce only from the supplicant.

   Fix this by generating a new ANonce when moving to the PTKSTART state
   for the purpose of starting new 4-way handshake to rekey PTK.

   Subject: [PATCH 6/8] TDLS: Reject TPK-TK reconfiguration

   Do not try to reconfigure the same TPK-TK to the driver after it has
   been successfully configured. This is an explicit check to avoid issues
   related to resetting the TX/RX packet number. There was already a check
   for this for TPK M2 (retries of that message are ignored completely), so
   that behavior does not get modified.

   For TPK M3, the TPK-TK could have been reconfigured, but that was
   followed by immediate teardown of the link due to an issue in updating
   the STA entry. Furthermore, for TDLS with any real security (i.e.,
   ignoring open/WEP), the TPK message exchange is protected on the AP path
   and simple replay attacks are not feasible.

   As an additional corner case, make sure the local nonce gets updated if
   the peer uses a very unlikely "random nonce" of all zeros.

   Subject: [PATCH 7/8] WNM: Ignore WNM-Sleep Mode Response without pending
    request

   Commit 03ed0a52393710be6bdae657d1b36efa146520e5 ('WNM: Ignore WNM-Sleep
   Mode Response if WNM-Sleep Mode has not been used') started ignoring the
   response when no WNM-Sleep Mode Request had been used during the
   association. This can be made tighter by clearing the used flag when
   successfully processing a response. This adds an additional layer of
   protection against unexpected retransmissions of the response frame.

   Subject: [PATCH 8/8] FT: Do not allow multiple Reassociation Response frames

   The driver is expected to not report a second association event without
   the station having explicitly request a new association. As such, this
   case should not be reachable. However, since reconfiguring the same
   pairwise or group keys to the driver could result in nonce reuse issues,
   be extra careful here and do an additional state check to avoid this
   even if the local driver ends up somehow accepting an unexpected
   Reassociation Response frame.

   To generate a diff of this commit:
   cvs rdiff -u -r1.17 -r1.18 pkgsrc/net/wpa_supplicant/Makefile
   cvs rdiff -u -r1.9 -r1.10 pkgsrc/net/wpa_supplicant/distinfo
   cvs rdiff -u -r0 -r1.1 \
       pkgsrc/net/wpa_supplicant/patches/patch-src_ap_ieee802__11.c \
       pkgsrc/net/wpa_supplicant/patches/patch-src_ap_wpa__auth.c \
       pkgsrc/net/wpa_supplicant/patches/patch-src_ap_wpa__auth.h \
       pkgsrc/net/wpa_supplicant/patches/patch-src_ap_wpa__auth__ft.c \
       pkgsrc/net/wpa_supplicant/patches/patch-src_ap_wpa__auth__i.h \
       pkgsrc/net/wpa_supplicant/patches/patch-src_common_wpa__common.h \
       pkgsrc/net/wpa_supplicant/patches/patch-src_rsn__supp_tdls.c \
       pkgsrc/net/wpa_supplicant/patches/patch-src_rsn__supp_wpa.c \
       pkgsrc/net/wpa_supplicant/patches/patch-src_rsn__supp_wpa__ft.c \
       pkgsrc/net/wpa_supplicant/patches/patch-src_rsn__supp_wpa__i.h \
       pkgsrc/net/wpa_supplicant/patches/patch-wpa__supplicant_wnm__sta.c