Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 7fa381f9 authored by Kevin Hufnagle's avatar Kevin Hufnagle Committed by android-build-merger
Browse files

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

Merge "docs: Updated link, wording associated with data-sharing IPC." into mnc-mr-docs am: c501688c am: 7bce49c5
am: 31d841c9

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

Change-Id: I82032bb7d831f436e8d05a16ab93aa27c3f660ef
parents 63b57feb 31d841c9

docs/html/training/articles/security-tips.jd

+10 −10
Original line number Diff line number Diff line
@@ -207,13 +207,13 @@ href="{@docRoot}guide/topics/manifest/permission-element.html#plevel">signature 
protection level</a> on permissions for IPC communication between applications

provided by a single developer.</p>



<p>Do not leak permission-protected data.  This occurs when your app exposes data

over IPC that is only available because it has a specific permission, but does

not require that permission of any clients of it’s IPC interface. More

details on the potential impacts, and frequency of this type of problem is

provided in this research paper published at USENIX: <a

href="http://www.cs.berkeley.edu/~afelt/felt_usenixsec2011.pdf">http://www.cs.be

rkeley.edu/~afelt/felt_usenixsec2011.pdf</a></p>

<p>Do not leak permission-protected data. This occurs when your app exposes

data over IPC that is available only because your app has permission to access

that data. The clients of your app's IPC interface may not have that same

data-access permission. More details on the frequency and potential effects

of this issue appear in <a class="external-link"

href="https://www.usenix.org/legacy/event/sec11/tech/full_papers/Felt.pdf"> this

research paper</a>, published at USENIX.