<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Python on P01NT</title><link>https://outofsrvc.github.io/en/tags/python/</link><description>Recent content in Python on P01NT</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 07 Aug 2026 00:30:00 +0300</lastBuildDate><atom:link href="https://outofsrvc.github.io/en/tags/python/index.xml" rel="self" type="application/rss+xml"/><item><title>Static Lab</title><link>https://outofsrvc.github.io/en/workshop/static-lab/</link><pubDate>Tue, 24 Mar 2026 10:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/static-lab/</guid><description>&lt;p>Bismillah&lt;/p>
&lt;p>In this article, we will solve a simple lab challenge that relies entirely on static analysis (Static Analysis). The objective here is to apply the concepts learned previously to decrypt the flag hidden within the program.&lt;/p>
&lt;blockquote>
&lt;p>Lab environment setup: You may download the executable for this lab from the following link &lt;a href="https://outofsrvc.github.io/assets/binaries/5t4t1c_cr4ckm3.7z">5t4t1c_cr4ckm3&lt;/a> in the course repository. The archive password is: &lt;strong>p01nt&lt;/strong>&lt;/p>&lt;/blockquote>
&lt;hr>
&lt;blockquote>
&lt;p>To open this file you must open it inside a &lt;strong>VM&lt;/strong>. Although I am the one who designed this file, never trust the cyber community. We will run the file with the following command&lt;/p></description></item><item><title>Dynamic Lab</title><link>https://outofsrvc.github.io/en/workshop/dynamic-lab/</link><pubDate>Wed, 25 Mar 2026 10:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/dynamic-lab/</guid><description>&lt;p>Bismillah&lt;/p>
&lt;p>In this article, we will solve a simple lab challenge that relies entirely on dynamic analysis using the x64dbg debugger. We assess that the exercise demonstrates how to bypass anti-debugging mechanisms and how to patch the program&amp;rsquo;s execution flow so that it accepts any key we provide.&lt;/p>
&lt;blockquote>
&lt;p>Lab environment setup: The executable for this lab can be downloaded from the following link &lt;a href="https://outofsrvc.github.io/assets/binaries/dyn4m1c_cr4ckm3.7z">dyn4m1c_cr4ckm3&lt;/a> in the course repository. Archive password: &lt;strong>p01nt&lt;/strong>&lt;/p></description></item><item><title>Flare-On 2014: Solving Challenge 1</title><link>https://outofsrvc.github.io/en/posts/flare-on-14-1/</link><pubDate>Fri, 07 Aug 2026 00:30:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/posts/flare-on-14-1/</guid><description>&lt;p>بسم الله&lt;/p>
&lt;p>In this article, we are going to solve the first challenge of &lt;strong>Flare-On (2014)&lt;/strong>. We will rely — for this challenge and for most of the upcoming ones — on the &lt;strong>Just-in-Time Learning&lt;/strong> methodology, also known as &lt;strong>Learning-by-Doing&lt;/strong>.&lt;/p>
&lt;h2 id="why-did-we-start-with-flare-on">Why Did We Start with Flare-On?&lt;/h2>
&lt;p>Because these challenges are built around real-world techniques, and they are not just artificial CTF puzzles as commonly presented in competitions.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Important note:&lt;/strong> CTF challenges are only a bridge between theoretical learning and hands-on practice. They do not, in any way, prove that you are an expert in the field. Real experience is gained by working with real-world programs — whether malware, games, or software we reverse engineer.&lt;/p></description></item></channel></rss>