<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Permissions on Florence Njeri</title>
    <link>https://florencenjeri.com/tags/permissions/</link>
    <description>Recent content in Permissions on Florence Njeri</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 22 Jul 2026 09:30:00 +0000</lastBuildDate><atom:link href="https://florencenjeri.com/tags/permissions/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Android Permissions and Component Exposure</title>
      <link>https://florencenjeri.com/posts/android_permissions/</link>
      <pubDate>Wed, 22 Jul 2026 09:30:00 +0000</pubDate>
      
      <guid>https://florencenjeri.com/posts/android_permissions/</guid>
      <description>Android Permissions and Component Exposure # Permissions are the layer that decides who is allowed to talk to what on an Android device. During a pentest, this is usually where the interesting bugs live: an app that exports too much, a permission with the wrong protection level, or a receiver that trusts anyone who can send it an intent. This post walks through the pieces you should be checking in every engagement, from the manifest down to custom permissions.
Exported vs Non-Exported Components # The strongest protection against a malicious app is simple: do not export the component in the first place.</description>
    </item>
    
  </channel>
</rss>
