<?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 Ajojose on Medium]]></title>
        <description><![CDATA[Stories by Ajojose on Medium]]></description>
        <link>https://medium.com/@ajojose12345678910?source=rss-f12a2333f88c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*FmoCQkLqLb-BYLqW</url>
            <title>Stories by Ajojose on Medium</title>
            <link>https://medium.com/@ajojose12345678910?source=rss-f12a2333f88c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:48:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ajojose12345678910/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[A Team Cannot Run on Telepathy: Aligning Around What Matters]]></title>
            <link>https://medium.com/@ajojose12345678910/a-team-cannot-run-on-telepathy-aligning-around-what-matters-498d42e76b20?source=rss-f12a2333f88c------2</link>
            <guid isPermaLink="false">https://medium.com/p/498d42e76b20</guid>
            <category><![CDATA[behavioral-science]]></category>
            <category><![CDATA[article-writing]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Ajojose]]></dc:creator>
            <pubDate>Wed, 18 Nov 2026 14:18:30 GMT</pubDate>
            <atom:updated>2026-11-18T14:18:30.204Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>A Team Cannot Run on Telepathy: Aligning Around What Matters</strong></p><p>On putting people before personal gains, reducing ego, communicating better, and building teams that actually work.</p><p>There is a difference between agreeing with a principle and actually practising it.</p><p>Most of us would agree that honesty is important. We would agree that teamwork is better than individual competition. We would agree that egos should not get in the way of collective goals.</p><blockquote>But what happens when these beliefs are put to the test?</blockquote><blockquote>What happens when someone disagrees with us? When a teammate misses a deadline? When our personal interests conflict with the team&#39;s interests? When we have to choose between getting credit for our work and helping someone else succeed?</blockquote><p>This is where principles become interesting. They stop being words and start influencing our decisions.</p><p>My time with First Principle Labs has made me think more about this distinction. Its guiding principles of People over Personal, Process over Person, and Progress over Perfection offer a useful way to approach collaboration.</p><h3>But how do I make sure that I follow them myself? How do I bring the people around me along?</h3><p>I don&#39;t have all the answers. However, a game we played during our last fellows&#39; meet gave me a good place to start.</p><h4>1. People over Personal: What are we actually trying to win?</h4><p>One of the most interesting experiences from our last meet was a game that made us think about individual gains and collective outcomes.</p><p>It made me realise something simple.</p><p>Sometimes, the best outcome for everyone comes from choosing cooperation over competition.</p><p>When we focus only on our individual gains, we might make decisions that seem beneficial in the short term. But those decisions can come at the cost of everyone else. In the end, even we might be worse off.</p><p>This is something I find particularly interesting about FPL&#39;s philosophy.</p><p>A society cannot make meaningful progress if everyone is constantly trying to get ahead at the expense of others. We need people who are willing to cooperate, share knowledge, and work towards something bigger than themselves.</p><p>I think the same applies to smaller teams.</p><p>A team is not a collection of individuals trying to maximise their own contributions. It is a group of people trying to create an outcome that would be difficult to achieve alone.</p><p>This also makes me think about ego.</p><p>How often do we defend an idea simply because it was ours? How often do we hesitate to appreciate someone else&#39;s work because we want our contribution to be noticed? How often does a disagreement turn into a personal argument?</p><p>I want to become better at separating my identity from my ideas.</p><p>Someone disagreeing with my approach does not mean they are disagreeing with me as a person. Someone pointing out a flaw in my work is not attacking my abilities.</p><p>One principle that I particularly like is to critique the work in public and the person in private.</p><p>We should be honest about what needs improvement. But that honesty should not come at the cost of someone&#39;s dignity.</p><p>I would rather work with someone who tells me directly when something is wrong than someone who agrees with everything and leaves problems unaddressed.</p><p>For me, People over Personal also means being honest, direct, and willing to put the collective outcome before personal ego.</p><h4>2. An uncomfortable realisation: I need to stop holding myself back</h4><p>There is one aspect of People over Personal that I am still trying to understand.</p><p>Putting people before personal interests should not mean completely ignoring your own needs.</p><p>I sometimes hesitate to approach someone because I feel that I might be wasting their time. I might want to ask a question, start a conversation, or seek someone&#39;s perspective. But I end up holding back.</p><p>I convince myself that I am being considerate.</p><p><strong><em>But am I?</em></strong></p><p>I could be making that decision on behalf of the other person without even giving them a choice. They might have been perfectly happy to talk.</p><p>I think I need to become a little more assertive. I need to pursue things that genuinely interest me. I need to be comfortable approaching people and asking questions.</p><p>There is a difference between being selfish and taking responsibility for your own growth.</p><p>I also need to be more intentional about my commitments. Saying yes to every opportunity does not mean I am making the best use of my time.</p><p>I have learnt that enthusiasm without prioritisation can become counterproductive.</p><p>I cannot expect to contribute meaningfully to a team if I am constantly spreading myself too thin.</p><p>Perhaps alignment starts with being honest about what I can contribute, what I want to learn, and what I need from others.</p><h4>3. Process over Person: A team cannot run on telepathy</h4><p>Let&#39;s consider a very familiar situation.</p><p>A team has four members. Everyone knows the deadline. Everyone agrees to complete their respective tasks.</p><p>One person is waiting for information from another. Someone else assumes that the first person has already started. Another member is unsure about what exactly needs to be done.</p><p>The deadline arrives.</p><p>The work is incomplete.</p><p>Who is responsible?</p><p>It is tempting to point fingers. But perhaps the problem started much earlier.</p><p>Maybe the responsibilities were never clearly defined. Maybe the expectations were different. Maybe someone needed help but never communicated it. Maybe nobody thought to check whether things were moving as planned.</p><p>This is why I think communication is one of the biggest factors in team alignment.</p><p><em>Miscommunication</em> can cause unnecessary friction. Delayed communication can make small problems much bigger.</p><p>A simple update can save a team from several hours of confusion.</p><p>I would rather someone tell me early that they cannot complete a task than discover it at the deadline. We can work around an obstacle when we know it exists.</p><p>We cannot fix a problem that nobody talks about.</p><p>But good communication alone is not enough. We also need good systems.</p><p>I think teams should establish a few basic things before getting into the actual work.</p><p>- Clear ownership: Every task should have someone responsible for it.<br>- Clear expectations: People should know what needs to be delivered and when.<br>- Regular communication: Everyone should know when and where to share updates.<br>- Early escalation: People should feel comfortable communicating when something goes wrong.<br>- Fallback plans: The team should know what happens when someone is unavailable or a task gets delayed.</p><p>These do not need to be complicated systems. Sometimes a shared task board and a short weekly check-in are enough.</p><p>The point is to reduce dependence on assumptions.</p><p>A good process should make it easier for people to do good work. It should not become another obstacle.</p><blockquote>When something goes wrong repeatedly, I would first look at the process. Was the task explained properly? Did the person have the resources? Was the responsibility clear?</blockquote><p>This does not mean people should escape <em>accountability</em>.</p><p>It means accountability should help us identify what needs to change. It should not become an excuse to blame someone.</p><h4>4. Give people a reason to care</h4><p>Another thing I have been thinking about is motivation.</p><p>We often divide work among team members and expect everyone to complete their tasks. But simply assigning work does not guarantee that people will be interested in doing it.</p><p>People need to understand why their contribution matters.</p><p>Take this article itself as an example.</p><p>Someone might look at writing an article as just another fellowship assignment. They might complete it because there is a deadline.</p><p>But there is more to it.</p><p>Writing can improve communication skills. It helps us organise our thoughts. It forces us to understand a subject instead of just having a vague opinion about it. Publishing also exposes our ideas to feedback.</p><p>Once people understand these benefits, the task becomes more meaningful.</p><p>I believe this applies to most team activities.</p><p>Before assigning a task, we should be able to explain its purpose. What does the team gain from it? What does the individual learn from it? How does it contribute to the larger outcome?</p><p>Not every task will be exciting. That is fine.</p><p>But people should at least understand why they are doing it.</p><p>Of course, this does not remove the need for accountability. A shared goal still requires people who are willing to put in the work.</p><p>A good team cannot depend on one or two people carrying everyone else.</p><h4>5. Progress over Perfection: Start, learn, and improve</h4><p>I think this principle is especially important when working with people.</p><p>We often spend too much time trying to get everything right before taking action.</p><p>We wait for everyone to be available. We wait for the perfect plan. We wait until we are completely confident about our approach.</p><p>Meanwhile, nothing moves.</p><p>I would rather have a team that starts with a reasonable plan and improves along the way.</p><p>The first version of a process might not work. A meeting schedule might be inconvenient. A task division might turn out to be inefficient.</p><p><strong><em>That is not necessarily a failure.</em></strong></p><p>It is information we can use to improve.</p><p>This also requires us to become more comfortable with feedback.</p><p>If someone points out a problem, we should not immediately become defensive. We should try to understand what they are saying.</p><p>The same applies when giving feedback.</p><p>There is a difference between telling someone that their work needs improvement and making them feel that they are not good enough.</p><p>I want to practise being direct without being unnecessarily harsh.</p><p>I also want to become better at receiving criticism without letting my ego take over.</p><p>The objective should always be to improve the work.</p><p>Not to prove who was right.</p><h4>6. How do we make these principles part of a team&#39;s culture?</h4><blockquote>Understanding these principles individually is one thing. Making them part of a team&#39;s everyday behaviour is another.</blockquote><p>I don&#39;t think a one-time discussion or a presentation about values is enough.</p><p>People might agree with everything during a meeting. But that does not mean they will remember those principles when deadlines are approaching and disagreements arise.</p><h3>We need systems that make good behaviour easier to practise.</h3><p>Here are a few things I would like to introduce in a team:</p><p>Start with shared expectations.</p><p>Before beginning a project, everyone should understand the objective, their responsibilities, and what success looks like.</p><p>Make communication a habit.</p><p>A short, regular update can prevent several problems. People should not have to chase each other for basic information.</p><p>Create room for disagreement.</p><p>People should be allowed to question decisions. Different perspectives can improve the final outcome. Disagreement should remain focused on the idea and the work.</p><p>Build fallback systems.</p><p>People have other commitments. Unexpected things happen. A team should not come to a complete stop because one person is unavailable. Important tasks should have clear backups and an agreed way to handle delays.</p><p>Reflect instead of assigning blame.</p><p>When something goes wrong, discuss what happened. Identify what could have prevented it. Make changes where necessary.</p><p>Most importantly, these practices should apply to everyone. They should not depend on who is leading the team or who has the most experience.</p><blockquote>I also like the idea of <em>Community × Accountability × Outcome.</em></blockquote><p>Community gives us a reason to work together. Accountability ensures that we take responsibility for our contributions. Outcome reminds us why we started in the first place.</p><h3>All three matter.</h3><p>A community without accountability can become a group where nobody takes ownership. Accountability without community can become a system of pressure. And without a meaningful outcome, both can lose direction.</p><h4>7. Alignment does not mean uniformity</h4><p>There is one thing I want to avoid when thinking about team alignment.</p><p>I do not want everyone to think exactly like me.</p><p>A team made up of people with identical opinions would probably agree quickly. But it would also miss out on different perspectives.</p><p>People bring different experiences, strengths, and ways of approaching problems.</p><p>We should not try to remove those differences.</p><p>Instead, we should establish enough trust to work through them.</p><p>I want to be part of a team where people can disagree openly. Where someone can say that an idea will not work without worrying about offending its creator. Where people can ask for help without feeling inadequate.</p><p>That requires effort from everyone.</p><p>It requires us to reduce our egos. It requires us to communicate clearly. It requires us to give others the benefit of the doubt.</p><p>And it requires us to remember that the person across the table is working towards the same outcome, even when their approach is different.</p><p>The real test of alignment</p><p>I am still figuring out how to practise these principles consistently. I do not think I will get everything right.</p><p>I will probably have moments when my ego gets in the way. I might communicate poorly. I might take on too much or fail to speak up when I should.</p><p>But I think that is exactly why these principles need to be practised rather than simply memorised.</p><p>I want to become someone who is honest enough to speak up, humble enough to listen, and responsible enough to follow through.</p><p>I want to work with people who care about the collective outcome. I want us to build systems that support each other without removing individual accountability. I want disagreements to improve our work rather than damage our relationships.</p><p>And most importantly, I want to stop measuring success only by what I achieve individually.</p><p>A team is not aligned because everyone agrees. It is aligned because everyone is willing to take responsibility for the same outcome.</p><h3>That is the kind of team I want to build.</h3><h3>And that is the kind of person I want to become.</h3><p>*/Thanks everyone for making it till the end of the article 🫶. I am new to writing and any kind of feedback is deeply appreciated. Thanks again/*</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=498d42e76b20" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ENIGMA DAY 5]]></title>
            <link>https://medium.com/@ajojose12345678910/enigma-day-5-0704c97982a3?source=rss-f12a2333f88c------2</link>
            <guid isPermaLink="false">https://medium.com/p/0704c97982a3</guid>
            <dc:creator><![CDATA[Ajojose]]></dc:creator>
            <pubDate>Mon, 06 Jul 2026 19:28:33 GMT</pubDate>
            <atom:updated>2026-07-06T19:28:33.957Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*feE97QotrjybMEYQy3eZJw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pJGYbLuaM7FT-u48J077Bw.png" /></figure><p>1 Opened the provided barcelona.pcap file using <strong>Wireshark</strong>.</p><p>2 Inspected the captured traffic and followed the <strong>first TCP Stream</strong>.</p><p>3 Found the encoded string: fWRvb2dfdDBuX3MxX2xtNFl7QU1HSU5F==</p><p>4 Decoded the string using a <strong>Base64 decoder</strong>, which produced: }doog_t0n_s1_lm4Y{AMGINE</p><p>5 Noticed that the decoded text was reversed. Reversed the string to obtain:ENIGMA{Y4ml_1s_n0t_good}</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0704c97982a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ENIGMA DAY 4 TASK]]></title>
            <link>https://medium.com/@ajojose12345678910/enigma-day-4-task-cfea0b6590dc?source=rss-f12a2333f88c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cfea0b6590dc</guid>
            <dc:creator><![CDATA[Ajojose]]></dc:creator>
            <pubDate>Mon, 06 Jul 2026 19:22:41 GMT</pubDate>
            <atom:updated>2026-07-06T19:22:41.460Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1bRzUcOYHAmJ4s5akJO4ZQ.png" /></figure><p>So yea this screenshot shows what i did</p><ol><li>I used strings command and got these</li></ol><p>Enter the activation key:<br>Access Denied! Wrong key.<br>GhidraIsAwesome123!<br>Access Granted! Here is your flag: %s</p><p>2. Then I gave the permission to execute using chmod +x</p><p>3. Then run the file which prompted for the activation key and hence the flag was found</p><p>Access Granted! Here is your flag:<br>picoCTF{r3v_3ng_1s_fUn_a8d9c2b4}</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfea0b6590dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enigma day3]]></title>
            <link>https://medium.com/@ajojose12345678910/enigma-day3-e6eedc677cf7?source=rss-f12a2333f88c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6eedc677cf7</guid>
            <dc:creator><![CDATA[Ajojose]]></dc:creator>
            <pubDate>Thu, 02 Jul 2026 16:22:18 GMT</pubDate>
            <atom:updated>2026-07-03T16:54:39.989Z</atom:updated>
            <content:encoded><![CDATA[<p>So I was given a code</p><h4>U0VBUkNIIFRIRSBVU0VSTkFNRSBPTiBQT1BVTEFSIFNJVEVTIChUV0lUVEVSL1gsIEZBQ0VCT09LKQoKVVNFUk5BTUU6IGxvcmVuem8xNDc2ClBBU1NXT1JEOiBSZXF1aWVzY2F0ITE0NzY=</h4><p>I decoded the base64 and it was</p><h3>SEARCH THE USERNAME ON POPULAR SITES (TWITTER/X, FACEBOOK) USERNAME: lorenzo1476<br>PASSWORD: Requiescat!1476</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s5ntFIRIg0hVk__bFeA_jw.png" /></figure><p>There was a login in that site but yea it wasnt it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*to66T1wSF_bh2jSrueNA-w.png" /></figure><p>I cant find anything with google searches. So I thought of searching on X as it said. I just cant believe that the normal search didnt gimme the X link. Wasted a lotta time for no reason</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XY531I0CBHLfxxL5H7GJmg.png" /></figure><p>Ok so I got the comment in one of the posts which was a base64 encoded</p><h4>dGhlIHBhdGggZW5kcyB3aXRoIDY0IGJhc2UgJ2JHOXZhM01nYkdsclpTQmhJR0poYzJVNU1pQjBieUJ0WlNkTVluWjJUMVUxVjNRL09HNXZLVXBlTFVkVGRFOVdZMVFrT0hWWVdUZzVXa291Smo1WlJsdG1aMVpvZDFneldGVTBLVWtoVUd3c0t5ay9WREpZSXk1TVIycDJKaXBuWXlnMVZWTlJianhzZGtkbkowUTdjek5NT2o1RlJEeHVhbDFGUUR3dGMyWXdPMjFPUFVrbic=</h4><p>It translated to the path ends with 64 base ‘bG9va3MgbGlrZSBhIGJhc2U5MiB0byBtZSdMYnZ2T1U1V3Q/OG5vKUpeLUdTdE9WY1QkOHVYWTg5WkouJj5ZRltmZ1Zod1gzWFU0KUkhUGwsKyk/VDJYIy5MR2p2JipnYyg1VVNRbjxsdkdnJ0Q7czNMOj5FRDxual1FQDwtc2YwO21OPUkn’ which seemed like a byte literal. I tried decoding it but never reached anywhere. And I understood this was not it. <strong>Back to Zero.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8jdOg15VjEt04vwekZnNfw.png" /></figure><p>I found a lnk to this site in another comment and I used the credentials to login but it was a dead end. There was nothing useful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G8KYy3TBcw1rBPymqCmEMg.png" /></figure><p>There was only one last comment left which was treated as potentially spam. It was a base64 and there it is I got the flag. Lets gooooo</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2uSbih4QtJk1g5vPDtP_Bw.png" /></figure><p><strong>ENIGMA{HAHA_fake_flag}</strong></p><p>It was a really fun CTF. Appreciate the effort.</p><p>Alright so I didnt realise it actually read fake flag. So In that page i logged in there was a comment</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Hpcd1QEjnepRR5HJQY-Nw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GiowM8RjNNOyK-g61wAAlg.png" /></figure><p>So put that in the url. And in this terminal i found a “clue.txt” file</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kr1kwdUuQCHuS-2H69zOcw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XCIoU7zV0h5mIoHGw4rQ6Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*9N9Wqo4xlopV_QaXNEuvxw.png" /></figure><p>changed it to locked and got the flag</p><h3>ENIGMA{Archive_Secured_Before_The_Templars}</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6eedc677cf7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Exploitation for Enigma CTF]]></title>
            <link>https://medium.com/@ajojose12345678910/web-exploitation-for-enigma-ctf-cf451774a6ea?source=rss-f12a2333f88c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf451774a6ea</guid>
            <dc:creator><![CDATA[Ajojose]]></dc:creator>
            <pubDate>Thu, 02 Jul 2026 15:34:34 GMT</pubDate>
            <atom:updated>2026-07-02T15:34:34.204Z</atom:updated>
            <content:encoded><![CDATA[<p>Today’s task was to find a hidden piece of content left somewhere on a website.</p><p>Website: <a href="https://pitchscope.netlify.app/">https://pitchscope.netlify.app/</a></p><p>So the challenge was pretty simple on the surface but needed a sharp eye. My mission was to explore the site, inspect everything carefully, follow the clues, and uncover the secret hidden within Argentina’s road to glory.</p><p>Step 1: Inspecting the Page</p><p>The very first thing I did was open up the page source using Ctrl + U and also had DevTools open on the side. If you’re doing web exploitation, inspecting the page is basically rule number one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uuH1BBP3wo1aXvgQvSHz5Q.png" /></figure><p>And yeah, I spotted something right away. There was a comment hiding in the HTML with a weird looking string that had a ‘=’ sign at the end. That’s basically Base64 waving at you.</p><p>Step 2: Decoding the Message</p><p>I threw the string into CyberChef and decoded it from Base64. The output?</p><p>/Argentina2022</p><p>That forward slash was a dead giveaway. It looked like a URL path so I just added it to the end of the site’s URL and hit enter.</p><p>Step 3 : Found the Login Page</p><p>It took me straight to a login page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uBLBNi4nHkau0kR73KVvZg.png" /></figure><p>The username was already there staring at me: LionelMessi. Cool. Now I just needed the password. Went back to the inspector one more time and found another comment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4srxWFeD7M8td_VdPXqb0A.png" /></figure><p>Password: Rosario</p><p>At this point I was like okay this is too easy lol. Entered both credentials and logged in.</p><p>Step 4 — The Flag</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FgykFc5bZhQnZ9ERrjCz3A.png" /></figure><p>Flag: ENIGMA{MESSI_FINALLY_COMPLETED_FOOTBALL}</p><p>Lessons Learned</p><p>1. Always inspect the page. Seriously, always.<br>2. HTML comments are goldmines in CTF challenges. Don’t skip them.<br>3. If you see a string ending in ‘=’ or ‘==’, think Base64 first.</p><p>Feedback on the Challenge</p><p>1. Really fun challenge that gets you thinking like an attacker.<br>2. Learned a lot about how small misconfigurations in the real world can lead to big vulnerabilities.</p><p>Conclusion</p><p>Sometimes the biggest discoveries aren’t on the page itself. They’re hiding just underneath it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf451774a6ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 1 — OSINT Walkthrough | Finding a Truck from a Single Photograph]]></title>
            <link>https://medium.com/@ajojose12345678910/day-1-osint-walkthrough-finding-a-truck-from-a-single-photograph-fd877eda15e9?source=rss-f12a2333f88c------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd877eda15e9</guid>
            <dc:creator><![CDATA[Ajojose]]></dc:creator>
            <pubDate>Tue, 30 Jun 2026 05:51:56 GMT</pubDate>
            <atom:updated>2026-06-30T05:51:56.006Z</atom:updated>
            <content:encoded><![CDATA[<p>The challenge provided only one image of a truck carrying a vehicle and tasked us with recovering the truck’s VIN. With no obvious identifiers visible, the investigation had to begin with the surroundings rather than the truck itself.</p><p>First things first, I checked the metadata and properties</p><h3>Step 1: Examining the Scene</h3><p>Instead of focusing solely on the truck, I carefully inspected every environmental clue in the image. The most useful observations included:</p><ul><li>Road marking <strong>OR-31</strong></li><li>A green directional sign pointing toward <strong>Silver Lake</strong></li><li>A distinctive red metal building beside the highway</li><li>Utility poles, road layout, and nearby parked vehicles</li></ul><p>These seemingly minor details became the foundation of the investigation.</p><h3>Step 2: Geolocating the Photograph</h3><p>Using Google Maps and Street View, I searched along <strong>Oregon Route 31</strong> near Silver Lake. By comparing the road geometry, the red building, driveway, utility poles, and surrounding landscape, I was able to identify the exact Street View location where the photograph had been captured.</p><h3>Step 3: Matching the Truck</h3><p>With the correct Street View panorama located, I confirmed that the truck in the challenge image matched the one captured by Google’s Street View vehicle. I checked the side and there it is VIN KJ291981</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7vxFAhQW1_V8tuG6Dh77lQ.png" /></figure><h3>Conclusion</h3><p>This challenge was an excellent example of practical OSINT. Rather than relying on obvious identifiers, I used environmental clues to geolocate the image and successfully locate the exact truck in Google Street View. It reinforced how powerful small details can be when combined with systematic investigation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd877eda15e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 1 — Crypto Walkthrough | Peeling Back Multiple Layers of Encoding]]></title>
            <link>https://medium.com/@ajojose12345678910/day-1-crypto-walkthrough-peeling-back-multiple-layers-of-encoding-0795e928a685?source=rss-f12a2333f88c------2</link>
            <guid isPermaLink="false">https://medium.com/p/0795e928a685</guid>
            <dc:creator><![CDATA[Ajojose]]></dc:creator>
            <pubDate>Tue, 30 Jun 2026 05:45:39 GMT</pubDate>
            <atom:updated>2026-06-30T05:45:39.276Z</atom:updated>
            <content:encoded><![CDATA[<p>The Day 1 Crypto challenge presented a mysterious encoded string and hinted that there were multiple layers hiding beneath the surface.</p><p>Unlike many beginner challenges, simply decoding Base64 once would not reveal the answer.</p><h3>Step 1: Base64 Decode</h3><p>The provided string was first decoded using Base64.</p><p>The result looked unusual:</p><pre>b&#39;TFVQTlRIe2pobHpoeV9rM2p5OXdhM2tfbTAyMTI3NTh9IA==&#39;</pre><p>This wasn’t the flag — it was a Python bytes literal.</p><h3>Step 2: Remove the Bytes Wrapper</h3><blockquote>The next step was removing the b’’ and it ended with = so it was base64 again</blockquote><h3>Step 3: Base64 Decode Again</h3><p>Running Base64 a second time produced:</p><pre>LUPNTH{jhlzhy_k3jy9wa3k_m0212758}</pre><p>At this point the challenge description made perfect sense:</p><blockquote><em>Keep decoding. You’re not at the bottom of the rabbit hole yet.</em></blockquote><h3>Step 4: Identifying the Final Cipher</h3><p>The expected flag format was:</p><pre>ENIGMA{...}</pre><p>However, the decoded text began with:</p><pre>LUPNTH</pre><p>Since both contain six letters, this strongly suggested that the final layer was not another encoding but a classical substitution cipher.</p><p>Testing common Caesar shifts revealed that a shift of <strong>−7</strong> converted:</p><pre>LUPNTH into ENIGMA</pre><pre>Applying the same shift to the entire message revealed the final flag.</pre><h3>Final Flag</h3><pre>ENIGMA{caesar_d3cr9pt3d_f0212758}</pre><h3>What I Learned</h3><p>This challenge highlighted an important distinction:</p><ul><li><strong>Encoding</strong> transforms data into another representation.</li><li><strong>Encryption (ciphers)</strong> intentionally hides information.</li></ul><p>The complete decoding chain was:</p><pre>Encoded String<br>        ↓<br>Base64<br>        ↓<br>Python Bytes Literal<br>        ↓<br>Base64<br>        ↓<br>Caesar Cipher (-7)<br>        ↓<br>Final Flag</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0795e928a685" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Basic Networking Commands]]></title>
            <link>https://medium.com/@ajojose12345678910/basic-networking-commands-eccb20c91846?source=rss-f12a2333f88c------2</link>
            <guid isPermaLink="false">https://medium.com/p/eccb20c91846</guid>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[wsl]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Ajojose]]></dc:creator>
            <pubDate>Thu, 30 Apr 2026 05:52:22 GMT</pubDate>
            <atom:updated>2026-04-30T05:52:22.814Z</atom:updated>
            <content:encoded><![CDATA[<p>The <strong>ip</strong> command is used to view and manage IP addressing on a system. <strong>ip -4 addr</strong> is used to display IPv4 addresses, and <strong>ip -6 addr</strong> is used to display IPv6 addresses assigned to network interfaces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RJG8eIVGJhKudkgHwI596w.png" /></figure><p>The <strong>ping</strong> command is used to test network connectivity. It sends <strong>ICMP packets</strong> to a web address or IP address to check whether the destination host is reachable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*ZVAvhVr_EsISKlBArP6QTA.png" /></figure><p>The ss command is used to display detailed information about network connections, sockets, and network activity. It is faster and more modern than netstat. ss -a shows all sockets (both listening and non-listening), ss -t displays TCP connections, and ss -u shows UDP connections. You can use ss -l to list only listening ports, and combine options like ss -lt to view listening TCP ports. The ss -s command provides a summary of socket statistics, while ss -p shows the processes using each socket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q8fTfZLUor6rhV6OU7OLgA.png" /></figure><p>The <strong>traceroute</strong> command is used to trace the path taken by packets from the source system to a destination. <strong>traceroute site-name</strong> traces the route to a specified website, while <strong>traceroute -I site-name</strong> performs tracing using ICMP packets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*072_YLgKVhF1vjmyImtlUg.png" /></figure><p>Configuring a <strong>static IP address</strong> means assigning a fixed IP address to a network interface instead of using DHCP. For example, a system can be assigned a static IP such as <strong>192.168.1.100</strong> so that the address remains unchanged after reboot.</p><p>In <strong>Ubuntu</strong>, static IP configuration is done using files inside the <strong>/etc/netplan/</strong> directory. These configuration files define the IP address, gateway, and DNS servers for the network interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*nzA2Qg6DC_ir-A9oFLDb2g.png" /></figure><p>After configuring a static IP address, <strong>network services</strong> must be applied or restarted so the changes take effect and the system can communicate properly on the network.</p><p>Troubleshooting network connectivity is done by managing network services using <strong>systemctl</strong>. Stopping the network service can simulate a connectivity failure, while restarting or re-enabling the service can restore network connectivity and confirm whether the issue is service-related.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*qur9pc0GdBmsmxTRwoeDCg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XVlu5SksR4RkXBBNw8e7mw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f_37pjqyD9a3QyMIhMiHdQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eccb20c91846" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Infinity Loop: Demystifying the 8 Phases of the DevOps Lifecycle]]></title>
            <link>https://medium.com/@ajojose12345678910/the-infinity-loop-demystifying-the-8-phases-of-the-devops-lifecycle-d5da1fa08f65?source=rss-f12a2333f88c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5da1fa08f65</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[operations]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Ajojose]]></dc:creator>
            <pubDate>Sat, 25 Apr 2026 12:38:26 GMT</pubDate>
            <atom:updated>2026-04-25T12:38:26.740Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How integrating development and operations creates a continuous engine for software delivery speed, reliability, and quality.</em></p><p>In modern software engineering, the days of throwing code over the wall to the operations team are over. To build fast, scale reliably, and maintain high quality, teams rely on the DevOps lifecycle — a continuous, iterative process that merges Development (Dev) and Operations (Ops).</p><p>Rather than a straight line with a final destination, DevOps is an “infinity loop.” It consists of eight interconnected phases where the end of one cycle directly feeds the beginning of the next.</p><p>Here is the architectural flow of that lifecycle.</p><h3>The DevOps Infinity Loop</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gft98JSrU_qBWMepYWurnw.gif" /><figcaption>DevOps simple diagram</figcaption></figure><h3>The 8 Phases of Continuous Delivery</h3><h4>1. Plan 📝</h4><p>Before writing a single line of code, teams must align on what needs to be built and why. This phase bridges business requirements with technical execution.</p><ul><li><strong>Key Activities:</strong> Defining project requirements, creating product roadmaps, managing backlogs, sprint planning, and writing user stories.</li><li><strong>Common Tools:</strong> Jira, Trello, Azure Boards, Asana.</li></ul><h4>2. Code 💻</h4><p>With a clear plan in place, developers begin translating user stories into functional software. Collaboration and version control are the lifeblood of this phase.</p><ul><li><strong>Key Activities:</strong> Writing code, conducting peer code reviews, branching, and merging changes safely.</li><li><strong>Common Tools:</strong> Git, GitHub, GitLab, Bitbucket</li></ul><h4>3. Build 🏗️</h4><p>Source code written by multiple developers is integrated and compiled into executable builds or deployable packages. This phase is heavily automated to catch integration issues early.</p><ul><li><strong>Key Activities:</strong> Continuous Integration (CI), code compilation, dependency management, and artifact creation.</li><li><strong>Common Tools:</strong> Jenkins, Maven, Gradle, GitHub Actions.</li></ul><h4>4. Test 🧪</h4><p>Quality cannot be an afterthought. In DevOps, testing shifts “left,” meaning it happens as early and automatically as possible to prevent bugs from reaching production.</p><ul><li><strong>Key Activities:</strong> Automated unit testing, integration testing, regression testing, and security scanning (DevSecOps).</li><li><strong>Common Tools:</strong> Selenium, JUnit, TestNG, Cypress.</li></ul><h4>5. Release 📦</h4><p>Once a build passes all automated tests, it is officially marked as a release candidate. This phase bridges the gap between development and live environments.</p><ul><li><strong>Key Activities:</strong> Configuration management, final approvals, release staging, and packaging for target environments.</li><li><strong>Common Tools:</strong> Jenkins, Bamboo, UrbanCode, AWS CodePipeline.</li></ul><h4>6. Deploy 🚀</h4><p>The automated rollout of the approved code into staging or production environments. A mature DevOps pipeline allows for multiple seamless deployments a day without user disruption.</p><ul><li><strong>Key Activities:</strong> Release orchestration, blue-green deployments, canary releases, and automated rollback planning.</li><li><strong>Common Tools:</strong> Kubernetes, Docker, Ansible, ArgoCD.</li></ul><h4>7. Operate ⚙️</h4><p>Once the software is live, the focus shifts to maintaining system health, ensuring maximum uptime, and managing infrastructure efficiently.</p><ul><li><strong>Key Activities:</strong> Infrastructure as Code (IaC) provisioning, server management, scaling, and incident response.</li><li><strong>Common Tools:</strong> Terraform, Puppet, Chef, AWS CloudFormation.</li></ul><h4>8. Monitor 📊</h4><p>The loop closes — and instantly restarts — here. Monitoring involves keeping a constant pulse on the live application to gather data on performance and user experience.</p><ul><li><strong>Key Activities:</strong> Tracking system health, log analysis, setting up alerting mechanisms, and analyzing user behavior.</li><li><strong>Common Tools:</strong> Prometheus, Grafana, ELK Stack (Elasticsearch, Logstash, Kibana), Datadog.</li></ul><h3>Closing the Loop</h3><p>The true power of DevOps lies in the arrow connecting <strong>Monitor</strong> back to <strong>Plan</strong>. The insights, bug reports, and performance metrics gathered in production directly inform the backlog for the next sprint. It is a perpetual engine of continuous improvement, ensuring that the software gets faster, safer, and better with every single rotation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5da1fa08f65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[☁️ Understanding Cloud Computing Models]]></title>
            <link>https://medium.com/@ajojose12345678910/%EF%B8%8F-understanding-cloud-computing-models-aa970df578cc?source=rss-f12a2333f88c------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa970df578cc</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[cloud-models]]></category>
            <dc:creator><![CDATA[Ajojose]]></dc:creator>
            <pubDate>Sat, 25 Apr 2026 11:59:33 GMT</pubDate>
            <atom:updated>2026-04-25T11:59:33.457Z</atom:updated>
            <content:encoded><![CDATA[<p>Cloud computing is basically everywhere now, like when you stream movies or a company runs its whole operation online. I think the main way people talk about it is through these three models, IaaS, PaaS, and SaaS, but they each work a bit differently depending on what you need.</p><p>Take IaaS for example, which stands for Infrastructure as a Service. It gives you things like virtual machines and storage over the internet, so instead of buying your own servers, you just rent them from somewhere like Amazon Web Services or Microsoft Azure. You end up controlling the operating system and the applications you put on there, while the provider takes care of the hardware and the data centers. That seems pretty flexible, especially if a company wants a custom setup or needs a lot of computing power.</p><p>Netflix uses something like that, I believe, with AWS to handle streaming all over the world. Its in the media and entertainment side of things. Companies that need full control over servers or networking pick IaaS a lot, like developers or big tech teams.</p><p>PaaS is Platform as a Service, and it provides this ready environment for building apps. You do not have to mess with servers or scaling, the platform handles that, like Heroku or Google App Engine. So developers can just focus on writing code and deploying stuff. It helps teams get things out faster, which is why startups use it to launch apps without all the infrastructure hassle.</p><p>That part gets a bit messy when you think about who it is for, mostly developers and product teams, or even SaaS businesses in tech. It feels like it speeds up productivity, but sort of skips the low level stuff.</p><p>Then there is SaaS, Software as a Service, where you get full applications right over the internet, no setup needed. Things like Salesforce for managing customers, or Shopify for online stores, or even Slack for chatting. You just use the software, and the provider does everything else. Its convenient and low cost, perfect for businesses or non technical users who want ready made tools like email or CRM or e-commerce.</p><p>Retail and sales industries rely on that a ton. I might be oversimplifying, but it seems like if you do not want to deal with maintenance, SaaS is the way to go.</p><p>Sometimes companies choose based on what fits, like IaaS for heavy control, PaaS for quick development, and SaaS for ease. When you need to focus only on coding, PaaS makes sense, or for full server access, IaaS. But not everything is clear cut, some overlap probably happens.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa970df578cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>