<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Challenges - Category - Rivit's blog</title><link>https://rivit.dev/categories/challenges/</link><description>Challenges - Category - Rivit's blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 13 Apr 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://rivit.dev/categories/challenges/" rel="self" type="application/rss+xml"/><item><title>Open-sourcing community CTF challenges</title><link>https://rivit.dev/posts/open-sourcing-community-ctf-challenges/</link><pubDate>Mon, 13 Apr 2026 12:00:00 +0000</pubDate><author><name>Rivit</name></author><guid>https://rivit.dev/posts/open-sourcing-community-ctf-challenges/</guid><description><![CDATA[<p>I <a href="https://github.com/rivit98/ctf-challenges/tree/master/community" target="_blank" rel="noopener noreferrer">open-sourced</a> a set of community CTF challenges I created for <a href="https://ctflearn.com/" target="_blank" rel="noopener noreferrer">CTFlearn</a>. The collection is intentionally pragmatic: small, self-contained puzzles you can run locally (Docker is provided), iterate on, and learn from.</p>
<h2 id="what-is-in-the-repository" class="headerLink">
    <a href="#what-is-in-the-repository" class="header-mark"></a>What is in the repository</h2><p>The repository contains 20+ challenges across four categories:</p>
<ul>
<li>pwn: the largest category — small networked binaries and local pwn problems covering memory corruption, information leaks, non-standard allocators, and ROP-style exploitation.</li>
<li>reversing: reverse-engineering puzzles and binary-analysis tasks.</li>
<li>misc: utility and puzzle-style problems that do not fit the categories above.</li>
<li>crypto: a small, crypto-related puzzle.</li>
</ul>
<p>All challenges ship with simple infrastructure to run them locally: Dockerfiles, a compose profile, solver scripts, and a short README. The repository README includes quick-start hints.</p>]]></description></item></channel></rss>