<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>reverse engineering on Reverse Engineering</title>
    <link>https://reverse.put.as/tags/reverse-engineering/</link>
    <description>Recent content in reverse engineering on Reverse Engineering</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>reverser@put.as (fG!)</managingEditor>
    <webMaster>reverser@put.as (fG!)</webMaster>
    <copyright>&amp;copy; 2025 fG!</copyright>
    <lastBuildDate>Fri, 20 Oct 2023 13:36:20 +0100</lastBuildDate><atom:link href="https://reverse.put.as/tags/reverse-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Attacking the heart of an OpenRG modem</title>
      <link>https://reverse.put.as/2023/10/20/attacking-the-heart-of-an-openrg-modem/</link>
      <pubDate>Fri, 20 Oct 2023 13:36:20 +0100</pubDate>
      <author>reverser@put.as (fG!)</author>
      <guid>https://reverse.put.as/2023/10/20/attacking-the-heart-of-an-openrg-modem/</guid>
      <description>Note: the original post was written in 2017 when there weren&amp;rsquo;t many posts discussing direct attacks to firmware flash. It also took a while to get in touch with the ISP to give them a chance to fix some of the issues described (in particular the ACS access) and then it was left in draft mode until today. I just made a quick revision and fixed quite a few dead links.</description>
    </item>
    
  </channel>
</rss>
