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

am: 31d841c

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

Change-Id: I82032bb7d831f436e8d05a16ab93aa27c3f660ef
This commit is contained in:
Kevin Hufnagle
2016-04-27 03:17:35 +00:00
committed by android-build-merger

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.