<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ctf on David An</title>
    <link>https://davidan.dev/tags/ctf/</link>
    <description>Recent content in ctf on David An</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 04 Jul 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://davidan.dev/tags/ctf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>UIUCTF&#39;23 OSINT Writeups</title>
      <link>https://davidan.dev/posts/uiuctf/</link>
      <pubDate>Tue, 04 Jul 2023 00:00:00 +0000</pubDate>
      
      <guid>https://davidan.dev/posts/uiuctf/</guid>
      <description>A long overdue set of writeups (solutions) for UIUCTF23. Recently I had the opportunity to help run UIUCTF 2023, a student-run capture the flag (CTF) event with some awesome folk in SIGPwny. The part I worked on mainly centered around open source intelligence (OSINT) techniques. In this post, we go over some solutions to the OSINT suite as some tips and tricks to approaching these challenges in CTFs.
Designing the Challenges One of the biggest things I wanted to do while designing these challenges were to be able to tell a story along all the challenges.</description>
    </item>
    
  </channel>
</rss>
