diff options
| author | Jouni Malinen <jouni@qca.qualcomm.com> | 2012-11-23 17:05:47 +0200 |
|---|---|---|
| committer | Dmitry Shmidt <dimitrysh@google.com> | 2012-11-26 14:50:27 -0800 |
| commit | 70fd8a038c4b825f7585881cb26c68db516ad77a (patch) | |
| tree | 9498e15a712b9f0164618b1799e065b6caf41979 /src/eap_server | |
| parent | 84d2de985ec73d5c12bd03cc0b8bbb0d24be4689 (diff) | |
| download | android_external_wpa_supplicant_8-70fd8a038c4b825f7585881cb26c68db516ad77a.tar.gz android_external_wpa_supplicant_8-70fd8a038c4b825f7585881cb26c68db516ad77a.tar.bz2 android_external_wpa_supplicant_8-70fd8a038c4b825f7585881cb26c68db516ad77a.zip | |
Android: Force group access to ctrl_iface directory
wpa_supplicant is started from /init.*.rc on Android and that seems
to be using umask 0077 which would leave the control interface
directory without group access. This breaks things since Wi-Fi
framework assumes that this directory can be accessed by other
applications in the wifi group. Fix this by adding group access even
if umask value would prevent this.
In most cases, this issue was not hit since the control interface
directory is normally created by that same init.*.rc file with suitable
mode and wpa_supplicant is killed in the way that does not allow it to
remove the file. However, if wpa_supplicant is allowed stop cleanly, it
will remove the directory and the next start could result with the Wi-Fi
framework not being able to use Wi-Fi (and GUI not showing Wi-Fi getting
enabled).
Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
Diffstat (limited to 'src/eap_server')
0 files changed, 0 insertions, 0 deletions