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

Commit 422ac4eb authored by Kevin Hufnagle's avatar Kevin Hufnagle
Browse files

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

A paragraph under the "Requesting Permissions" section of the
"Security Tips" page discusses the complications associated with
sharing data over inter-process communication (IPC) when the clients
involved have different permission settings. This paragraph now
includes a working link and clearer wording to describe the concept.

Bug: 26807597
Change-Id: I35e316f5f97d4ec45d9beaae95424221e6a92da5
parent 566c9be6

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.