Spurious newlines output while writing the config file can corrupt the wpa_supplicant configuration. Avoid writing these for the network block parameters. This is a generic filter that cover cases that may not have been explicitly addressed with a more specific commit to avoid control characters in the psk parameter. RM-290 Signed-off-by: Paul Stewart <pstew@google.com> Git-commit: 0fe5a234240a108b294a87174ad197f6b5cb38e9 Git-repo: git://w1.fi/srv/git/hostap.git Change-Id: I35e8483bdda5c391b95da42c2f577d5e9217f2e2 CRs-fixed: 1007548
RM-290 Collides with mainline updates This reverts commit b79e09574e50e168dd5f19d540ae0b9a05bd1535. Change-Id: If4b4b834b5e3e5e582e8be93038d69635f8a42dd
RM-290 Collides with mainline updates This reverts commit b845b81ec6d724bd359cdb77f515722dd4066cf8. Change-Id: I4726aa01ec8441cf1b75163c994df147cdd0fdd1
This was previously handled for the case where the non-success Invitation Response frame was sent out during the Listen phase. However, in the case the Action frame TX ended up getting scheduled when the Search phase scan had already started (e.g., due to the driver reporting Invitation Request RX late enough for the Listen-to-Search transition having already started), the postponed Action frame TX status processing did not cover the specific case of non-success Invitation Response. This could result in the p2p_find operation getting stopped (stuck in SEARCH state) unexpectedly Fix this by calling p2p_check_after_scan_tx_continuation() from Invitation Response TX callback handler if the invitation was rejected. RM-290 CRs-Fixed: 1002261 Git-commit: 3433721c5f9073c0d45c1109b825f1dcbabbf517 Git-repo : git://w1.fi/srv/git/hostap.git Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com> Change-Id: Ic045516f31520fbe8ba068c88fe247df1746f29a
Add Transmit Power Envelope element defined in IEEE P802.11-REVmc/D4.3, 8.4.2.161. RM-290 Git-commit: 3c417499e71b0c7f2dfae69fb1b67eb31e467ba6 Git-repo : git://w1.fi/srv/git/hostap.git CRs-Fixed: 979946 Change-Id: Ib3e11ee78cbe8e4d875d6c43dc2ec5539043fdb1 Signed-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
This new parameter allows hostapd to add Vendor Specific elements into (Re)Association Response frames similarly to the way vendor_elements parameter can be used for Beacon and Probe Response frames. RM-290 Git-commit: a9112270615dd68d422623ebc26c21a6887a2a11 Git-repo : git://w1.fi/srv/git/hostap.git Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com> Change-Id: I033aced040c894f4dc4791c4e5081135976ebd0c CRs-Fixed: 1003412
Parent thread exits when daemonize. This will cause child threads to die and eap_proxy_post_init is not executed To fix this, child thread should be created after demonize RM-290 Change-Id: Ibd9e3dc79cb1a7650b3adc55afdc95818a2e011b CRs-Fixed: 1032710
Commit 0603bcb7fe8babf183362518238c142afe8e2036 ('hostapd: Process MAC
ACLs on a station association event (SME in driver)') processes MAC ACL
on a station association event for drivers which use AP SME offload but
does not consider the scenario where the drivers offload ACL. This can
result in station disconnection, though the driver accepts the
connection. Address this by avoiding the hostapd ACL check for the
drivers offloading MAC ACL.
RM-290
CRs-Fixed: 1031991
Git-commit: bb4e19e3f4c9d1973279b3b768bc0539ee7cb962
Git-repo : git://w1.fi/srv/git/hostap.git
Change-Id: I2934fbf676c803059e62ba2436c1181efb05a294
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Many of the global configuration parameters are written as strings without filtering and if there is an embedded newline character in the value, unexpected configuration file data might be written. This fixes an issue where wpa_supplicant could have updated the configuration file global parameter with arbitrary data from the control interface or D-Bus interface. While those interfaces are supposed to be accessible only for trusted users/applications, it may be possible that an untrusted user has access to a management software component that does not validate the value of a parameter before passing it to wpa_supplicant. This could allow such an untrusted user to inject almost arbitrary data into the configuration file. Such configuration file could result in wpa_supplicant trying to load a library (e.g., opensc_engine_path, pkcs11_engine_path, pkcs11_module_path, load_dynamic_eap) from user controlled location when starting again. This would allow code from that library to be executed under the wpa_supplicant process privileges RM-290 Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com> Git-commit: 2a3f56502b52375c3bf113cf92adfa99bad6b488 Git-repo: git://w1.fi/srv/git/hostap.git Change-Id: Ibb1eeb6b727c27ecc4a2efce57f5394e98051061 CRs-fixed: 1007548
Most of the cred block parameters are written as strings without filtering and if there is an embedded newline character in the value, unexpected configuration file data might be written. This fixes an issue where wpa_supplicant could have updated the configuration file cred parameter with arbitrary data from the control interface or D-Bus interface. While those interfaces are supposed to be accessible only for trusted users/applications, it may be possible that an untrusted user has access to a management software component that does not validate the credential value before passing it to wpa_supplicant. This could allow such an untrusted user to inject almost arbitrary data into the configuration file. Such configuration file could result in wpa_supplicant trying to load a library (e.g., opensc_engine_path, pkcs11_engine_path, pkcs11_module_path, load_dynamic_eap) from user controlled location when starting again. This would allow code from that library to be executed under the wpa_supplicant process privileges RM-290 Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com> Git-commit: b166cd84a77a6717be9600bf95378a0055d6f5a5 Git-repo: git://w1.fi/srv/git/hostap.git Change-Id: Ib8222446297317f4e57bdb49597fdf6d19554886 CRs-fixed: 1007548