Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "docs: Updated link, wording associated with data-sharing IPC." into mnc-mr-docs

Browse Source 
am: c501688

* commit 'c501688ce5ef620586e682203d239f010e77cd44':
  docs: Updated link, wording associated with data-sharing IPC.

Change-Id: Icc09241ddad8900a4c03ee0ba467a7631152bc7d
This commit is contained in:
Kevin Hufnagle
2016-04-11 22:43:57 +00:00
committed by android-build-merger
parent 6d683d2003 c501688ce5
commit 7bce49c5f1
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/html/training/articles/security-tips.jd
View File

@@ -207,13 +207,13 @@ href="{@docRoot}guide/topics/manifest/permission-element.html#plevel">signature
protection level</a> on permissions for IPC communication between applications protection level</a> on permissions for IPC communication between applications
provided by a single developer.</p> provided by a single developer.</p>
<p>Do not leak permission-protected data. This occurs when your app exposes data <p>Do not leak permission-protected data. This occurs when your app exposes
over IPC that is only available because it has a specific permission, but does data over IPC that is available only because your app has permission to access
not require that permission of any clients of it’s IPC interface. More that data. The clients of your app's IPC interface may not have that same
details on the potential impacts, and frequency of this type of problem is data-access permission. More details on the frequency and potential effects
provided in this research paper published at USENIX: <a of this issue appear in <a class="external-link"
href="http://www.cs.berkeley.edu/~afelt/felt_usenixsec2011.pdf">http://www.cs.be href="https://www.usenix.org/legacy/event/sec11/tech/full_papers/Felt.pdf"> this
rkeley.edu/~afelt/felt_usenixsec2011.pdf</a></p> research paper</a>, published at USENIX.