<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IPC on Florence Njeri</title>
    <link>https://florencenjeri.com/tags/ipc/</link>
    <description>Recent content in IPC on Florence Njeri</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 22 Jul 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://florencenjeri.com/tags/ipc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pentesting Android Services</title>
      <link>https://florencenjeri.com/posts/android_services/</link>
      <pubDate>Wed, 22 Jul 2026 09:00:00 +0000</pubDate>
      
      <guid>https://florencenjeri.com/posts/android_services/</guid>
      <description>Pentesting Android Services # Services are the Android component that runs long-lived work in the background. Think of an app that keeps uploading large files, plays audio while the UI is closed, or syncs data on a schedule. Like every other component, a Service has to be declared in AndroidManifest.xml under the &amp;lt;service&amp;gt; tag, and even when it is exported it can be locked down further with android:permission.
Why does this matter? Because a Service is often the piece of the app that actually does the privileged work: talking to internal APIs, touching files, or moving data between processes. If another app can reach that Service from outside the sandbox, it can effectively borrow the victim app&amp;rsquo;s privileges to run those internal actions.</description>
    </item>
    
  </channel>
</rss>
