- Aug 10, 2016
-
-
Janis Danisevskis authored
Bug: 22914603 Change-Id: I8ae1a786702694ca2bb8707a4c142b8a233042ee
-
- Aug 08, 2016
-
-
dcashman authored
Change-Id: I2593e100bdad420d0d988fbaeb8d2ec259b8df1d
-
Treehugger Robot authored
- Aug 05, 2016
-
-
Daniel Micay authored
am: cbd7b182 Change-Id: I5933e92a19410a5cb51af6e15b5a4d45487df699
-
Daniel Micay authored
am: 5e6aa65f Change-Id: I0e9dbefe4f393b13662bf9a520c878de5f221397
-
dcashman authored
Change-Id: I16706423534069f69bd0305ac500a9cd74db55a6
-
TreeHugger Robot authored
-
William Roberts authored
am: 9cd46da0 -s ours Change-Id: Ic7780a46482d5767f7eb0205ade16ec28a4a3a01
-
William Roberts authored
am: 006582cd Change-Id: I8b07c10415fe02c707da926f3f19e2a584c027b3
-
William Roberts authored
am: 98ff70cc Change-Id: Ia8d1ee546acddb9b19827e6db9d6ce1d8d25411d
-
Daniel Micay authored
These APIs expose sensitive information via timing side channels. This leaves access via the adb shell intact along with the current uses by dumpstate, init and system_server. The /proc/interrupts and /proc/stat files were covered in this paper: https://www.lightbluetouchpaper.org/2016/07/29/yet-another-android-side-channel/ The /proc/softirqs, /proc/timer_list and /proc/timer_stats files are also relevant. Access to /proc has been greatly restricted since then, with untrusted apps no longer having direct access to these, but stricter restrictions beyond that would be quite useful. Change-Id: Ibed16674856569d26517e5729f0f194b830cfedd
-
William Roberts authored
am: 2b33112a Change-Id: I08987ae7229ebbbbcf980be4aaef2eb8fb7e24da
-
Treehugger Robot authored
-
- Aug 04, 2016
-
-
William Roberts authored
boolean and setenforce macros are not used in base policy and cannot be used in any policy, since they violate neverallow rules. Remove these from the policy. Change-Id: Icc0780eaf06e95af36306031e1f615b05cb79869 Signed-off-by:
William Roberts <william.c.roberts@intel.com>
-
- Aug 03, 2016
-
-
John Stultz authored
am: f4600073 Change-Id: If145723bcbaee8cf5f7678707f7f155bf49fc841
-
John Stultz authored
am: 4a72e72a Change-Id: Ib5ea655ebdd322413f1f4c056628876b2d4cf7d7
-
John Stultz authored
am: e4025649 Change-Id: Ief8c1bb3927c2dca50459db8e71b330e0a58608e
-
John Stultz authored
am: 19b6485f Change-Id: I0574ab7e70a8b3d906a5b11368239d58d1d64e70
-
John Stultz authored
With v4.8+ kernels, CAP_WAKE_ALARM is needed to set alarmtimers via timerfd (this change is likely to be backported to stable as well). However, with selinux enabled, we also need to allow the capability on the system_server so this enables it. Change-Id: I7cd64d587906f3fbc8a129d48a4db07373c74c7e Signed-off-by:
John Stultz <john.stultz@linaro.org>
-
- Aug 02, 2016
-
-
Christopher Wiley authored
Bug: 30041228 Test: WiFi tethering, client mode continues to function Change-Id: I95a583ad4d57642f4731e415abb77732df5289ac
-
- Jul 29, 2016
-
-
Christopher Wiley authored
Stopping hostapd abruptly with SIGKILL can sometimes leave the driver in a poor state. Long term, we should pro-actively go in and clean up the driver. In the short term, it helps tremendously to send SIGTERM and give hostapd time to clean itself up. Bug: 30311493 Test: With patches in this series, wificond can cleanly start and stop hostapd in integration tests. Change-Id: Ic770c2fb1a1b636fced4620fe6e24d1c8dcdfeb8
-
- Jul 28, 2016
-
-
Christopher Wiley authored
-
TreeHugger Robot authored
-
- Jul 27, 2016
-
-
Elliott Hughes authored
am: 8da3ddd4 Change-Id: I6dddcd102ecb97c243868a7273f55e73cfb4d475
-
Elliott Hughes authored
am: c817c3b0 Change-Id: Id6bd5f7e772fd00e3adef6c5f9fbf537799b0aab
-
Elliott Hughes authored
am: 98fbb318 Change-Id: Ic7ffa7d6571647a165f83b47906f33908ac7745d
-
Elliott Hughes authored
am: aa2aa219 Change-Id: I5e1634a8c0cee6cb759e0acea086b68dbd21fb7e
-
Elliott Hughes authored
-
Martijn Coenen authored
Add a macro to make this easier for other processes as well. Change-Id: I489d0ce042fe5ef88dc767a6fbdb9b795be91601 (cherry picked from commit c2b9c1561e4bd7ac86d78b44ca7927994e781da0)
-
Martijn Coenen authored
Change-Id: I07d188e4dd8801a539db1e9f3edf82a1d662648e (cherry picked from commit 61a082a55dbc2798d50d0d4b766151d69334729a)
-
- Jul 26, 2016
-
-
William Roberts authored
Applications should not access /dev/input/* for events, but rather use events handled via the activity mechanism. Change-Id: I0182b6be1b7c69d96e4366ba59f14cee67be4beb Signed-off-by:
William Roberts <william.c.roberts@intel.com>
-
Elliott Hughes authored
Bug: http://b/30317429 Change-Id: I5c499c48d5e321ebdf588a162d29e949935ad8ee Test: adb shell dmesg | grep ueventd
-
Daniel Rosenberg authored
am: 249cb987 Change-Id: I4b3991f3d7efd049fe4d29c57c1e043b12cbd898
-
Daniel Rosenberg authored
am: 42a5f5e8 Change-Id: I2a30458bce94d7600aecedbc6bffbcca44c2669b
-