-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.xml
49 lines (40 loc) · 2.95 KB
/
index.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>xenocidewiki's blog</title>
<link>https://xenocide.wiki/</link>
<description>Recent content on xenocidewiki's blog</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
<copyright>© xenocide.wiki</copyright>
<lastBuildDate>Mon, 04 Jan 2021 01:25:00 +0100</lastBuildDate>
<atom:link href="https://xenocide.wiki/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>IceCTF 2020 | Hydrogen Bomb Writeup</title>
<link>https://xenocide.wiki/posts/icectf-hydrogen-bomb/</link>
<pubDate>Mon, 04 Jan 2021 01:25:00 +0100</pubDate>
<guid>https://xenocide.wiki/posts/icectf-hydrogen-bomb/</guid>
<description>Intro We are given a binary called bomb which is a billion functions taking input, where the goal is to find a sequence of inputs that gets us to a function called defuse which prints the flag.
We will embark on a journey that fried my brain and left me with two(!) out of the three braincells I already had remaining.
In order to get to defuse, we need to pass the following check:</description>
</item>
<item>
<title>X-Mas CTF 2019 | Kernel Crackme Writeup</title>
<link>https://xenocide.wiki/posts/xmas-ctf-kernel-crackme-writeup/</link>
<pubDate>Wed, 05 Feb 2020 02:15:00 +0000</pubDate>
<guid>https://xenocide.wiki/posts/xmas-ctf-kernel-crackme-writeup/</guid>
<description>For this challenge we are provided with two files, &ldquo;challenge.exe&rdquo; and &ldquo;X-MAS_kernel_crackme.sys&rdquo;.
I first looked at challenge.exe, but nothing particularly interesting is happening in there. It simply creates a service which is used to load the driver, asks for a license key, and then communicates with the driver making it do most of the work.
Looking at the image above it is evident that challenge.exe reads in a license key (I suppose this will be the flag), then sends it off to the driver using WriteFile, and we can guess that after the driver has done its work, challenge.</description>
</item>
<item>
<title>About</title>
<link>https://xenocide.wiki/about/</link>
<pubDate>Tue, 28 Jan 2020 20:34:09 +0000</pubDate>
<guid>https://xenocide.wiki/about/</guid>
<description>Hello!
I am xenocidewiki, a mathematics student at the University of Edinburgh. This is my blog where I will post random reverse engineering and programming content, as well as my writeups for various CTF challenges that I solve. I am currently playing for the cr0wn and focus on RE tasks.
I have rather broad interests, RE is naturally one of them, however I also thoroughly enjoy looking at things within cryptography, pwning or any type of exploitation really, the windows kernel, and game hacks.</description>
</item>
</channel>
</rss>