<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by N0flow on Medium]]></title>
        <description><![CDATA[Stories by N0flow on Medium]]></description>
        <link>https://medium.com/@n0flow?source=rss-9470d1994887------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zZymWSVULztI2huo7g_fiA.png</url>
            <title>Stories by N0flow on Medium</title>
            <link>https://medium.com/@n0flow?source=rss-9470d1994887------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:08:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@n0flow/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[From Zero to CPTS and OSCP in 11 Months: My Journey at 17]]></title>
            <link>https://medium.com/@n0flow/from-zero-to-cpts-and-oscp-in-11-months-my-journey-at-17-6f35b2bc4e95?source=rss-9470d1994887------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f35b2bc4e95</guid>
            <category><![CDATA[cpt]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[N0flow]]></dc:creator>
            <pubDate>Sat, 26 Sep 2026 07:33:44 GMT</pubDate>
            <atom:updated>2026-09-26T07:33:44.640Z</atom:updated>
            <content:encoded><![CDATA[<p>Eleven months. That’s all it took to go from having no practical cybersecurity experience to earning both the CPTS and OSCP certifications.</p><p>I am a 17-year-old Canadian living in Malaysia, and just a few days ago, I passed the Offensive Security Certified Professional (OSCP) exam on my first attempt.</p><p>In this blog, I want to share a brief overview of my journey. I try to cover the challenges I encountered and my experience attaining both the CPTS and OSCP certifications within 11 months in total.</p><p>It was an intense, 11-month, full-time grind that started the moment I finished high school. Instead of immediately heading to university, I convinced my mom to let me take a gap year to focus entirely on practical skills, basically certificates. :)</p><p>During those 11 months, I averaged about 6 to 8 hours of studying a day. That number actually factors in all my downtime, including the holidays, vacations, and sick days where I did zero work and just took a break.</p><p>My schedule definitely wasn’t a perfectly straight line. Some days I was completely locked in and pulled massive 10 to 12-hour marathons, while other days were zeroes. But when you look at the whole timeline, minus the actual exam days, it all balanced out to that steady 6 to 8-hour baseline.(Exam days were 12h +)</p><h3>Part 1: The Foundation</h3><p>When I started at 16, I had close to zero knowledge about Cybersecurity. My only exposure was a Harvard course I did a few years back named “CS50’s Introduction to Cybersecurity”, and all I remembered from that course was bruteforcing…</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*EyS6BQ9SE6hApwKr.gif" /></figure><p>I started my journey off by enrolling into the Google Cybersecurity Certificate, but I quickly realized it was too theoretical. While it provided a basic overview, I regret spending the $49 because it lacked the hands-on application I yearned for. However it does its job of providing an overall foundation of what cybersecurity itself is.</p><p>After completing my Google Cybersecurity course within a month or two I progressed by working through TryHackMe’s basic pathways, specifically Cybersecurity 101, Junior Pentesting and lastly Offensive Pentesting.</p><p>I was also grinding through two other major resources. For networking, I focused on doing the Jeremy’s IT Lab CCNA course, taking detailed notes until about Day 30. Simultaneously, I used pwn.college to build a good foundation in Linux. Balancing these three platforms was quite demanding, but proved to be helpful in the long run.</p><p>I spent a total of around 3 months on these resources altogether.</p><h3>Part 2: The HTB CPTS Grind</h3><p>With my foundations set, I moved on to the Hack The Box Certified Penetration Testing Specialist (CPTS) pathway.</p><p>I initially thought CPTS was just an exam, but discovering that there was also course material was an absolute game-changer!!!</p><p>You can read about the CPTS on their official website</p><p>This phase took me around three to four months of treating studying like a 9-to-5 job. The skill assessments were brutally difficult, particularly the Active Directory and password attack module. After doing them, the imposter syndrome hit realllyy hard, and I seriously questioned if I had chosen the right career path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*kcHj2uOZyPGMvwM3.gif" /></figure><p>One of the challenges I ran into while working through the course was figuring out how to structure my notes. What should I include? What should I leave out? I ended up revising my note-taking system countless times and spent a considerable amount of time researching different approaches.</p><p>With the help of AI, also <a href="https://www.youtube.com/@cyberryan">Cyber Ryan</a>, I was able to develop a note-taking and a methodology system that worked well for me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*5mDoU8L8OTPRam1B.gif" /></figure><p>After completing the course material finally, I started off by working through the CPTS track which took me some time but was worth it. I then transitioned into the IPPSEC’s CPTS playlist labs, attempting them myself except the “insane” difficulty boxes and both watching his video and writing my own mini writeups for all the labs.</p><p>The last preparation I did was doing the AEN module blind, which I kind of struggled with in some parts. Understanding why I struggled and reviewing the modules a couple times helped me realise my weaknesses. From there I made adjustments to my notes and methodology and then I decided to attempt the exam.</p><h4>CPTS EXAM</h4><p>The CPTS exam itself is a 10-day marathon where you must compromise an entire network. I personally used all the ten days, the first 6–7 days were for capturing the flags and the last 3–4 were for the report. My report came out to be 145 pages. (It was bigger but narrowed it down)</p><p>The biggest lesson I learned during this exam was the danger of rabbit holes. On Flag 8, I spent two full days banging my head against the wall on the simplest step because I refused to take a break and the same thing occurred on flag 10, which was the EASIEST FLAG!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*FdNMmZclxLOP8I1L.gif" /></figure><p>I eventually secured 12 out of the 14 flags, which was the minimum required to pass. I was so burnt out that I didn’t even attempt the final two flags and just worked on my report.</p><p>After I believe a week of submitting my report, I received the email that I passed the exam!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*-VxE9MedUBidUM8ci1j7jA.png" /></figure><p>Can’t find the email…</p><h3>A Note on AI and Reporting</h3><p>The CPTS requires a highly professional penetration testing report. Since this was my first time writing one, I leaned heavily on AI, to help format my executive summary and also helped with remediations and mitigations.</p><p>However, AI proved to be a double-edged sword. During the exam, it confidently suggested solutions that were completely wrong, leading me down further rabbit holes which cost me a good amount of time.</p><p>AI is an incredible tool for formatting and structuring a 140-page report, but it cannot replace actual human critical thinking.</p><h3>Part 3: The OSCP Sprint</h3><p>After recovering from the CPTS, I set my eyes on the OSCP (Offensive Security Certified Professional). Because of the high cost of the exam, the pressure was immense.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*IJ9q3AsPRrNIxe-7.gif" /></figure><p>The OSCP is basically a practical certification proving ethical hacking skills. It requires passing a 24-hour practical exam to compromise vulnerable target systems. You must then submit a penetration testing report within 24 hours after hacking ends.</p><p>You can read about the OSCP on their official website</p><p>I dedicated a total of one month and 20 days.</p><p>My strategy for the OSCP was highly focused: I relied almost entirely on Proving Grounds (PG Practice). I specifically targeted the “LAINS List,” working through Linux, Windows, and Active Directory boxes.</p><p>I intentionally avoided Hack The Box during this period because the methodology required for OSCP boxes is really different from HTB’s style.</p><p>I managed to complete the “LAINS List” pretty fast and still had around 5–7 days of subscription left to my PG, so I decided to complete the famous “TJ NULLS List”. There were only a couple extra linux labs and I believe one more AD lab within TJ’s list.</p><p>The PG boxes were really helpful in understanding the Offsec way of doing things and it definitely took some time to adjust to it. I struggled on the “Very Hard” labs and also a few of the “Medium” ones in the beginning of my PG journey but then after doing enough PG labs, It became quite easy and with the right knowledge at hand, I completed both lists within a month.</p><p>Huge thanks to TJNULL and Lainkusanagi for putting those lists together, they were incredibly helpful!</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*v7wDLTDthQsTdjrb.gif" /></figure><p>Completing the PG lab practice I went ahead and purchased the PEN-200, 3 month access.</p><p>I started by completing the modules within 3–4 days and taking notes, where I encountered new techniques or attack vectors I hadn’t come across before.(i.e. Client-Side attacks)</p><p>I then progressed forward and finished off most of the challenge labs except Relia(Completed 40%), Medtech, Skylark and Feast.</p><p>I did the three mock exams the last and tried to treat them like actual exams but unfortunately for the OSCP C, I had a lot of stuff going on so could not treat it as a mock and messed this mock up pretty bad (Only AD and couldn’t figure out and one of the standalones). Looking back, it was mainly due to getting frustrated easily, not being patient enough and overlooking the simple stuff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*fEMf-5w0zDumXOms.gif" /></figure><p>After that, I took some time to relax. I focused on refining my methodology, reviewing my notes and rereading all my mini writeups I created. Once I felt more confident, I took a few more days to rest before scheduling my exam.</p><p>In the time leading up to the exam, I spent a considerable amount of time browsing r/oscp on reddit looking for advice and learning from the experiences of others who had already taken the exam (Both failed and passed).</p><p>I also watched several Active Directory-focused videos, reviewed my methodology, and prepared my OSCP report template so that everything would be ready and smooth on exam day.</p><p>With my preparation complete, it was finally time to attempt the exam.</p><h4>OSCP EXAM:</h4><p>The exam overall was quite easy, I felt it to be slightly different to the mock exams, the AD was definitely different to the mock but it was really easy for me personally(Felt closer to CPTS format, but nowhere near in terms of difficulty). The standalones felt closer to the mock and also felt quite easy, except one of the standalones privilege escalation which took me a considerable amount of time to solve.</p><p>I managed to earn the passing grade within almost 7 hours(Including breaks and dinner) into the exam. The other 10 points took me around 2–3 hours and it was the privilege escalation on one of the standalones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*hGkP21Scg9qkldtp.gif" /></figure><p>After each flag, I would document my steps and capture the needed screenshots and paste them into Obsidian(Note-taking tool). After securing the 80 points, I went back to organizing my steps and screenshots. After doing so, I decided to head to bed.</p><p>I woke up a bit late, which left me around 6 hours to work with. From there, I tried to make a dent on the last standalone but it just wouldn’t budge. Two hours in and I decided it’s best I get working on my report.</p><p>I completed 90% of my report before the exam ended, mainly because I was scared that somehow I missed a critical screenshot…</p><p>After finishing my exam, I went over my report about ten times to make sure everything was clear. I then took a long break before rereading it another ten times and finally submitting it (Somehow every time I read it, I found a new mistake).</p><p>One day after submitting my report, the email finally arrived!</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*rn4FoXeTrK4GqvYfCoAwOw.png" /></figure><p>The preparation paid off, and I was fortunate enough to pass the OSCP, 80/100 on my first attempt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*LKEZFk6jWj8bJD8q.gif" /></figure><p>One thing I do a little differently, which I don’t necessarily recommend, is that I don’t always stick to my methodology. During both my CPTS and OSCP exams, I mostly followed my instincts. However, I always kept my methodology at hand and referred back to it whenever I got stuck.</p><p>I’m not proud of this habit, but it’s just how I’ve worked over time.</p><h3>What’s Next?</h3><p>I start university in two months.</p><p>Before then, I plan to go back and finish the AWS modules I skipped in the PEN-200 course.</p><p>I also have one more exam attempt and four months of subscription left for the HTB so I decided to go ahead and most probably finish the Certified Web Exploitation Specialist (CWES) pathway. I don’t really care much about the exam, rather the contents are more important to me. I am also doing some of the Seasonal Boxes on HTB.</p><p>I plan on doing a couple of other things like sharpening my programming capabilities, which is really weak. Possibly finding some work I could do and a lot more, but I have yet to make my decision.</p><h3>Final Thoughts</h3><p>Deciding to take a gap year was kind of a gamble, but looking back, it was the best choice I could have made. It was most definitely intense, exhausting, and there were plenty of times where self-doubt crept over the wall, but those very challenges I encountered forced me to level up in many different ways.</p><p>There wasn’t some you know hidden trick to getting through it. It really just came down to consistency, taking detailed notes, knowing when to walk away for a break, and documenting every mistake so I wouldn’t repeat it(wished I had done this earlier). Slowing down was way more valuable than trying to speed-run the course content.</p><p>For anyone starting out, my best advice is to slow down. Focus heavily on the fundamentals(Shoulda done that more), write your own mini write-ups for the labs you do, and engrain it in your brain that enumeration always comes before exploitation.</p><p>Hitting a wall of burnout is incredibly easy when you’re sacrificing a lot under tight time limits. But pushing through and proving to yourself that you can crack these environments is an unmatched feeling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*XZFiCAw9Mm45-U4_.gif" /></figure><p>Since I wanted to keep post not too long and also readable, I’m planning to drop a blog or YouTube video soon to share some specific tools, advice, and resources that I felt to be very helpful in my journey.</p><p>This is just the very beginning of my journey, and I hope putting this out there gives some momentum to those grinding through the exact same struggle.</p><p>Alhamdulillah!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f35b2bc4e95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I Learned From Hosting My First CTF]]></title>
            <link>https://medium.com/@n0flow/what-i-learned-from-hosting-my-first-ctf-41feee9e55e6?source=rss-9470d1994887------2</link>
            <guid isPermaLink="false">https://medium.com/p/41feee9e55e6</guid>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[N0flow]]></dc:creator>
            <pubDate>Sat, 26 Sep 2026 07:32:35 GMT</pubDate>
            <atom:updated>2026-09-26T07:45:22.946Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week I got to host my first CTF event with CyberSpectre.</p><p>I’ve done a decent number of CTFs myself and worked through a ton of labs on HTB and Proving Grounds, but being on the other side of it is a completely different experience.</p><p>Instead of solving challenges, I was the one building them, deploying them, testing them, keeping the infrastructure alive, helping people when they got stuck, and fixing things when they inevitably broke.</p><p>And yeah, some things broke.</p><h3>Building the challenges</h3><p>I put together around 25 challenges across a bunch of categories: web, forensics, Linux, OSINT, crypto, and misc.</p><p>The event was aimed at beginners, so my main goal was making sure not every challenge required a ton of prior CTF experience. I wanted someone fairly new to security to look at a challenge, poke around, find some clues, and actually work their way to a solution without feeling completely lost.</p><p>At the same time I didn’t want it to be all “find the obvious thing and grab the flag.” A few of the later challenges needed real exploitation techniques.</p><p>That balance was honestly one of the hardest parts of the whole thing. A challenge looks obvious when you’re the one who built it, because you already know exactly where everything is. The second someone else starts solving it, you realize it can be either painfully obvious and take a few mins or completely confusing depending on assumptions you didn’t even know you were making.</p><h3>Taking inspiration from other labs</h3><p>A lot of the ideas came from stuff I’ve run into while learning. I’ve spent a good amount of time on HTB and Proving Grounds, so of course that shaped how I approached things.</p><p>I didn’t want to just rip off existing machines though. I’d take a technique or idea I thought was interesting, like a certain enumeration method or forensic artifact, and build something smaller and different around it.</p><p>I also utilized AI for a lot of the basic challenge ideas, which proved to be actually very helpful and did implement a quite good amount of them.</p><p>Sometimes that worked great. Sometimes it sounded good in my head and turned out way less interesting once I actually built it, which led me to make countless changes and then deciding well its not good enough..</p><h3>My first time deploying vulnerable environments</h3><p>This was also my first time using CTFd, both as a platform and for actually running a CTF. I’d never used it before, even as a player, so pretty much the whole process was new to me.</p><p>Running a CTF platform and being responsible for the challenges behind it is a completely different experience from just solving them. I also made pretty heavy use of AI while creating the challenges, especially the full-style Linux labs. It helped a lot with building out parts of the environments, and getting things working and debugging issues.</p><p>There’s also a big difference between “this works on my machine” and “this needs to work for everyone at the event.”</p><p>Suddenly I had to think about things I’d never really had to worry about as a player. How are people accessing the challenges? What happens if something crashes? What needs to be restarted? What happens when multiple teams hit the same service at once? How do people know what they’re supposed to do? What happens when someone finds a way to solve a challenge that I never intended, which actually happended twice during the event.</p><p>Those questions become a lot more real when actual people are relying on your infrastructure.</p><h3>The inevitable hiccups</h3><p>There were some, obviously. A few challenges needed troubleshooting mid event, stuff crashed or needed restarting that I hadn’t planned for.</p><p>Looking back though, those problems were probably one of the most valuable parts of the whole thing. It’s easy to build something and assume it works because you tested it yourself. Running a live event exposes every assumption you didn’t realize you were making. Something that runs fine when you’re the only one touching it can behave completely differently with a bunch of teams hammering it at the same time.</p><p>That pushed me to think a lot harder about reliability, testing, and documentation, basically how someone who’s never seen my setup would actually experience it.</p><h3>A smaller first event</h3><p>Turnout wasn’t huge, but honestly I think that worked out for a first event. Smaller group meant I could actually keep track of what was going on and jump on issues fast. It also let me talk to participants and watch how they approached challenges, which mattered a lot since the whole thing was built for beginners.</p><p>You can think you made the intended path obvious, and then watching someone actually solve it tells you whether that’s true or not. Sometimes people found stuff I never expected. Sometimes they completely missed what I thought was the obvious hint. Both were useful to see in action.</p><h3>What I’d change next time</h3><p>I’d spend way more time testing challenges from the perspective of someone who’s never seen them before. I’d also think through deployment and recovery ahead of time instead of figuring it out mid event.</p><p>Difficulty balance is the other thing I want to get better at. Making a beginner friendly CTF is harder than it sounds. You want people to struggle enough that solving it feels good, but not so much they’re stuck for an hour with no idea where to look. That probably just takes more reps and more feedback from real participants.</p><h3>What I took away from it</h3><p>The biggest thing is realizing how different building security challenges is from solving them. As a player you only ever see the finished challenge. You don’t see the infrastructure, the testing, the unintended solves, the broken services at 2am, or the last minute fixes.</p><p>Hosting this made me appreciate all of that a lot more. It was a good reminder that cybersecurity isn’t just about popping boxes and grabbing flags. Building things, breaking your own assumptions, and fixing your own mess in real time teaches you just as much.</p><p>This was my first I hosted CTF and it definitely wasn’t perfect. But I learned more from the stuff that broke than from the stuff that went smoothly, and next time I’ll at least be able to apply the stuff I learnt during this event</p><p>Thanks to the CyberSpectre team, the volunteers, and everyone who showed up and played.</p><p>Alhamdulillah</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41feee9e55e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building My First Tool: How Reconductor Came Together]]></title>
            <link>https://medium.com/@n0flow/building-my-first-tool-how-reconductor-came-together-bd8be68a1644?source=rss-9470d1994887------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd8be68a1644</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[N0flow]]></dc:creator>
            <pubDate>Tue, 14 Jul 2026 18:45:20 GMT</pubDate>
            <atom:updated>2026-09-26T07:45:38.125Z</atom:updated>
            <content:encoded><![CDATA[<p>For a while now I’ve been heads down in labs, boxes, and certs, but everything I was doing was consuming other people’s tools. I hadn’t actually built anything of my own. So I set myself a small target: write a simple real tool, from scratch.</p><p>That’s how Reconductor started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/1*9dgEX6AVuCifShTxeDn4Rg.png" /></figure><h3>The Problem I Was Solving</h3><p>Recon is the first step on basically every box or engagement, and it’s almost always the same handful of Nmap commands. A full TCP sweep, a detailed version and script scan on the ports that came back open, sometimes a UDP pass.</p><p>The specific scan profiles I used weren’t random either. During OSCP I learned the hard way that running a single heavy scan straight away can actually miss ports, if the flags aren’t tuned right, a box under load or a slower connection can cause you to walk away thinking a port is closed when it isn’t. So I spent time tuning rate and searching online until I had profiles I trusted not to miss anything. I’ve been running those same tuned scans ever since, on OSCP boxes and on CTF’s, and they haven’t let me down… yet. Reconductor is really just those trusted commands turned into something I don’t have to retype every time.</p><h3>What Reconductor Does</h3><p>It’s a Python CLI wrapper around nmap. You give it a target IP, it shows you three scan profiles, and it runs the right nmap command for you:</p><ol><li>Full TCP scan across all 65535 ports, tuned for speed</li><li>A detailed scan with version detection and default scripts on ports you specify</li><li>A full sweep of the top 1000 UDP ports</li></ol><p>Nothing insane on the Nmap side, these are scan profiles I already trusted and used manually. What changed is that now I don’t have to remember or retype any of it for the millionth time. (Should though once in a while)</p><h3>Building It</h3><p>This was my first real script, so I kind of leaned on AI along the way, not to write it for me, but to help me get past dumb roadblocks I kept running into and to explain some of the things I encountered that I didn’t know yet, things like how to structure a CLI properly. The scan profiles, the logic, and the decisions behind what the tool should actually do were mine. (Still a lot of room for improvement)</p><h3>What I Learned</h3><p>Small as it is, this project taught me more than I expected:</p><ul><li>How to structure a CLI tool that takes arguments and handles bad input gracefully</li><li>Why something as simple as a .gitignore file actually matters</li><li>That “simple” tools still need real design decisions: what happens on invalid input, what gets saved, what the user actually sees</li></ul><h3>What’s Next</h3><p>Reconductor is intentionally small right now, and that’s fine, it was meant to be a first baby step, not a finished product. Next on the list maybe is a structured output per target instead of flat text files, and eventually feeding open ports from the full scan straight into the detailed scan automatically.</p><p>If you want to see the code, it’s up on my GitHub as Reconductor. If you’re on a similar path, self taught, building toward OSCP or just trying to get more hands on, my advice is the same thing that got me here: stop only using tools, and start building one, even a small one. :)</p><p>Github repo: <a href="https://github.com/N0fl0w/Reconductor-">https://github.com/N0fl0w/Reconductor-</a></p><p>Alhamdulillah</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd8be68a1644" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>