<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ghidra on Florence Njeri</title>
    <link>https://florencenjeri.com/tags/ghidra/</link>
    <description>Recent content in Ghidra on Florence Njeri</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 01 Dec 2024 09:36:41 +0000</lastBuildDate><atom:link href="https://florencenjeri.com/tags/ghidra/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reverse Engineering</title>
      <link>https://florencenjeri.com/posts/reverse_engineering/</link>
      <pubDate>Sun, 01 Dec 2024 09:36:41 +0000</pubDate>
      
      <guid>https://florencenjeri.com/posts/reverse_engineering/</guid>
      <description>Reverse Engineering # Decompiling a program from assemnly back to high level language to try and understand what the program does.
Example uses cases:
Vulnerability Analysis Malware Research Binary Analysis Tools Summary (Ghidra Book, Ch. 2) # 1. file # What: Identifies the file format (ELF, PE, Mach-O), architecture (x86, ARM), and bit-width (32/64-bit). When: Step 1 (Triage). Use it the moment you receive a mystery file. Why vs Others: Use this instead of nm or objdump initially because it tells you if the file is even an executable or if it is &amp;ldquo;stripped&amp;rdquo; (missing names). Example Command: file &amp;lt;filename&amp;gt; 2.</description>
    </item>
    
  </channel>
</rss>
