Android-x86
Fork
Spenden

  • R/O
  • HTTP
  • SSH
  • HTTPS

external-wpa_supplicant_8: Liste der Commits

external/wpa_supplicant_8


RSS
Rev. Zeit Autor
ea14e68 lollipop-x86 2015-10-06 14:43:24 Chih-Wei Huang

add private_lib for NL80211 driver.

Copied from hardware/broadcom/wlan/bcmdhd/wpa_supplicant_8_lib
with minor fixes for x86.

4cf0f2d 2015-07-10 06:02:51 Jouni Malinen

P2P: Validate SSID element length before copying it

This fixes a possible memcpy overflow for P2P dev->oper_ssid in
p2p_add_device(). The length provided by the peer device (0..255 bytes)
was used without proper bounds checking and that could have resulted in
arbitrary data of up to 223 bytes being written beyond the end of the
dev->oper_ssid[] array (of which about 150 bytes would be beyond the
heap allocation) when processing a corrupted management frame for P2P
peer discovery purposes.

This could result in corrupted state in heap, unexpected program
behavior due to corrupted P2P peer device information, denial of service
due to process crash, exposure of memory contents during GO Negotiation,
and potentially arbitrary code execution.

Thanks to Google security team for reporting this issue and smart
hardware research group of Alibaba security team for discovering it.

Change-Id: I9f350f20cdd010f2c096514b245b4a901ad74e46
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>

3264501 2015-02-09 23:09:30 The Android Automerger

merge in lmp-mr1-release history after reset to lmp-mr1-dev

0a217de 2015-02-06 08:46:52 Vinit Deshpande

Don't write to wpa_supplicant.conf directly

There is a chance that wpa_supplicant may get killed during
the time it is writing config file. If this happens, user
information like SSIDs and passwords can be lost forever.

This change works around that by writing config to a
temporary file and then renaming the file to the correct name.

Bug: 19224089

Change-Id: I1709cdd5e5c6dfa3073e42c644fae941b43401cc
Signed-off-by: Vinit Deshpande <vinitd@google.com>

d02cea1 2014-12-08 23:10:29 The Android Automerger

merge in lmp-mr1-release history after reset to lmp-mr1-dev

adaa28a 2014-12-05 03:12:50 Dmitry Shmidt

Merge "Return only full network line in list_networks" into lmp-mr1-dev

aeec9b8 2014-12-04 23:10:46 The Android Automerger

merge in lmp-mr1-release history after reset to lmp-mr1-dev

68c7ea4 2014-12-04 15:16:29 Vinit Deshpande

Merge "List all networks despite message limit of 4096 bytes" into lmp-mr1-dev

a7c60b4 2014-12-04 08:51:11 Jithu Jance

nl80211: Ignore Connect failure for the previous association

Suppose there are two APs (AP1 & AP2) and user attempted to connect to
AP2 before the previous connection with AP1 could succeed. Now, if the
connection event comes for the older AP with failed status, we should
just ignore it as the wpa_supplicant state has moved to "ASSOCIATING"
with the new AP (AP2).

This is a similar to the case where a disconnection event is ignored for
a case where local disconnect request can cause the extra event to show
up during the next association process following that command.

Signed-off-by: Jithu Jance <jithu@broadcom.com>
Signed-off-by: vandwalle <vandwalle@google.com>

9e37fc2 2014-12-04 04:48:46 Dmitry Shmidt

Return only full network line in list_networks

Change-Id: I81a74db1ba1e4e48397ce779687fffda42cbd8ac
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>

da134e9 2014-12-04 04:27:27 Vinit Deshpande

List all networks despite message limit of 4096 bytes

This change creates 'LIST_NETWORK LAST_ID=x' form to allow
retrieval of all networks saved in the system. Without this form,
only first few (whatever fills in first 4096 bytes) can be
retrieved.

Signed-off-by: Vinit Deshpande <vinitd@google.com>

cf510c9 2014-11-18 23:11:37 The Android Automerger

merge in lmp-mr1-release history after reset to lmp-mr1-dev

fee0f92 2014-11-18 07:53:11 Jouni Malinen

am 658fb4ad: Work around AP misbehavior on EAPOL-Key descriptor version

* commit '658fb4adb9458c3055c64a43833f1a9e89b4db74':
Work around AP misbehavior on EAPOL-Key descriptor version

658fb4a 2014-11-18 07:13:36 Jouni Malinen

Work around AP misbehavior on EAPOL-Key descriptor version

It looks like some APs are incorrectly selecting descriptor version 3
(AES-128-CMAC) for EAPOL-Key frames when version 2 (HMAC-SHA1) was
expected to be used. This is likely triggered by an attempt to negotiate
PMF with SHA1-based AKM.

Since AES-128-CMAC is considered stronger than HMAC-SHA1, allow the
incorrect, but stronger, option to be used in these cases to avoid
interoperability issues with deployed APs.

This issue shows up with "WPA: CCMP is used, but EAPOL-Key descriptor
version (3) is not 2" in debug log. With the new workaround, this issue
is ignored and "WPA: Interoperability workaround: allow incorrect
(should have been HMAC-SHA1), but stronger (is AES-128-CMAC), descriptor
version to be used" is written to the log.

Bug: 18411110

Change-Id: I9ae12e8882adc9e785f6e4cef9f30b89bf72dcd2
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>

fde887d 2014-11-11 23:11:42 The Android Automerger

merge in lmp-mr1-release history after reset to lmp-mr1-dev

2e425d6 2014-11-11 04:18:27 Dmitry Shmidt

Cumulative patch from commits: a7f5271 and 7465640

a7f5271 Update pending connect radio work BSS pointer on scan update
7465640 Invoke connect work done for all the connection failure cases

Bug: 18312770

Change-Id: I5e59edaac24c30bbfdab2e38e8ea902300b0308d
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>

5e7651a 2014-11-08 23:11:50 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

d5365eb 2014-11-06 23:12:30 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

b048789 2014-11-05 23:12:16 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

b07fed0 2014-11-04 23:11:42 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

9aeab01 2014-11-03 23:10:32 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

2951f7e 2014-11-02 23:10:16 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

d49608f 2014-11-01 22:10:31 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

07b23db 2014-10-30 22:10:29 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

eb3a1f8 2014-10-29 22:10:09 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

8e42087 2014-10-28 22:12:53 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

c30a260 2014-10-27 22:09:48 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

a666cec 2014-10-26 22:09:44 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

1c3b5ac 2014-10-25 22:10:28 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

ac7e5cf 2014-10-23 22:11:29 The Android Automerger

merge in lmp-mr1-release history after reset to a7b06faf528d1765cc2712cc9a31ad45d7c3110b

Show on old repository browser