<?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 Hamza Saidu on Medium]]></title>
        <description><![CDATA[Stories by Hamza Saidu on Medium]]></description>
        <link>https://medium.com/@hamzasaidu34?source=rss-cc0a164c9a4f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*arNRfINyB4Cyt3AV</url>
            <title>Stories by Hamza Saidu on Medium</title>
            <link>https://medium.com/@hamzasaidu34?source=rss-cc0a164c9a4f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:00:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hamzasaidu34/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[Building a Parcel Delivery System with PHP, HTML, CSS, and MySQL: An ALX Student’s Journey]]></title>
            <link>https://medium.com/@hamzasaidu34/building-a-parcel-delivery-system-with-php-html-css-and-mysql-an-alx-students-journey-21d127466688?source=rss-cc0a164c9a4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/21d127466688</guid>
            <category><![CDATA[alx-blog]]></category>
            <dc:creator><![CDATA[Hamza Saidu]]></dc:creator>
            <pubDate>Wed, 14 Jun 2023 14:14:14 GMT</pubDate>
            <atom:updated>2023-06-14T14:24:18.439Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="pds" src="https://cdn-images-1.medium.com/max/1024/1*G0DAOX-61FPl-PwHZcc1Ww.jpeg" /></figure><p><strong>Introduction</strong></p><p>In today’s fast-paced world, efficient parcel delivery systems play a vital role in ensuring timely and secure deliveries. This blog post explores the journey of an ALX student who successfully developed a robust parcel delivery system using PHP, HTML, CSS, and MySQL. We will delve into the process of learning PHP, deploying the system on web hosts, and highlight some challenges along the way, including how ChatGPT provided valuable assistance to overcome obstacles.</p><p><strong>Learning PHP: A Stepping Stone</strong></p><p>When I first started my journey to develop the parcel delivery system, I had little to no experience with PHP. However, with the comprehensive learning resources and guidance provided by ALX, I quickly grasped the fundamentals of PHP programming. The interactive exercises and real-world projects helped me understand the language’s syntax, functions, and object-oriented programming concepts.</p><p>With dedication and consistent effort, I was able to become proficient in PHP within a relatively short span of time.</p><p><strong>Designing the Interface</strong></p><p>To create an intuitive and user-friendly interface for the parcel delivery system, I utilized HTML and CSS. These front-end technologies allowed me to design an aesthetically pleasing website with smooth navigation and a responsive layout. I focused on creating an interface that was visually appealing and optimized for both desktop and mobile devices.</p><p><strong>Leveraging MySQL for Efficient Data Management</strong></p><p>A reliable database is essential for storing and managing parcel delivery information securely. I integrated MySQL, a popular open-source relational database management system, into the project.</p><p><strong>Deployment</strong></p><p>Deploying the System on Web Hosts: Taking the parcel delivery system from development to production involves deploying it on web hosts. I gained valuable experience in this process, learning how to select a suitable hosting provider, configure server settings, and upload files.</p><p><strong>Overcoming Challenges with the Help of ChatGPT</strong></p><p>Throughout the development process, the ALX student encountered several challenges. In times of uncertainty or roadblocks, they turned to ChatGPT for assistance. The blog post highlights specific instances where ChatGPT provided guidance, solutions, and recommendations. Whether it was debugging code, refining the user interface, or optimizing database queries, ChatGPT proved to be a valuable resource.</p><p><strong>Conclusion</strong></p><p>Developing a parcel delivery system using PHP, HTML, CSS, and MySQL is a significant achievement for any aspiring web developer. The process of learning these technologies, crafting an appealing user interface, leveraging a robust database management system, and deploying the system on web hosts. It also emphasizes the invaluable role of ChatGPT in overcoming challenges and providing guidance along the way. With dedication, perseverance, and the right tools, anyone can create innovative solutions to real-world problems.</p><ul><li><a href="https://github.com/Cyberguru1/Parcel-Delivery-System/blob/master/README.md">Link</a> to the GitHub link for the project</li><li><a href="https://parcled-delivery-service.000webhostapp.com/">Link</a> to the deployed project page</li><li><a href="https://qkpage1.co/p/PDS">Link</a> to the project’s landing page</li><li><a href="https://www.linkedin.com/in/hamza-saidu">Link</a> to your LinkedIn profile</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21d127466688" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pico CTF 2023 — Power Analysis: Warmup ( Cryptography ) 200points Unintended Solution ?]]></title>
            <link>https://medium.com/@hamzasaidu34/pico-ctf-2023-power-analysis-warmup-cryptography-200points-unintended-solution-cf6bfe320a4f?source=rss-cc0a164c9a4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf6bfe320a4f</guid>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[power-analysis]]></category>
            <category><![CDATA[ctf-writeup]]></category>
            <category><![CDATA[picoctf]]></category>
            <category><![CDATA[cryptography]]></category>
            <dc:creator><![CDATA[Hamza Saidu]]></dc:creator>
            <pubDate>Thu, 25 May 2023 21:46:00 GMT</pubDate>
            <atom:updated>2023-05-25T21:46:00.744Z</atom:updated>
            <content:encoded><![CDATA[<h4>Pico CTF 2023 — Power Analysis: Warmup ( Cryptography ) 200points Unintended Solution ?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*T67aCXWRXBVobjwaJqjP4g.png" /></figure><p>This challenge tends to demonstrates one of the famous side channel attacks out there, but this has to do with AES, starting the instance of the challenge, we see a file, downloading it and on opening we got</p><pre>#!/usr/bin/env python3<br>import random, sys, time<br><br>with open(&quot;key.txt&quot;, &quot;r&quot;) as f:<br>    SECRET_KEY = bytes.fromhex(f.read().strip())<br><br>Sbox = (<br>    0x63, 0x7C, 0x77, 0x7B, 0xF2, 0x6B, 0x6F, 0xC5, 0x30, 0x01, 0x67, 0x2B, 0xFE, 0xD7, 0xAB, 0x76,<br>    0xCA, 0x82, 0xC9, 0x7D, 0xFA, 0x59, 0x47, 0xF0, 0xAD, 0xD4, 0xA2, 0xAF, 0x9C, 0xA4, 0x72, 0xC0,<br>    0xB7, 0xFD, 0x93, 0x26, 0x36, 0x3F, 0xF7, 0xCC, 0x34, 0xA5, 0xE5, 0xF1, 0x71, 0xD8, 0x31, 0x15,<br>    0x04, 0xC7, 0x23, 0xC3, 0x18, 0x96, 0x05, 0x9A, 0x07, 0x12, 0x80, 0xE2, 0xEB, 0x27, 0xB2, 0x75,<br>    0x09, 0x83, 0x2C, 0x1A, 0x1B, 0x6E, 0x5A, 0xA0, 0x52, 0x3B, 0xD6, 0xB3, 0x29, 0xE3, 0x2F, 0x84,<br>    0x53, 0xD1, 0x00, 0xED, 0x20, 0xFC, 0xB1, 0x5B, 0x6A, 0xCB, 0xBE, 0x39, 0x4A, 0x4C, 0x58, 0xCF,<br>    0xD0, 0xEF, 0xAA, 0xFB, 0x43, 0x4D, 0x33, 0x85, 0x45, 0xF9, 0x02, 0x7F, 0x50, 0x3C, 0x9F, 0xA8,<br>    0x51, 0xA3, 0x40, 0x8F, 0x92, 0x9D, 0x38, 0xF5, 0xBC, 0xB6, 0xDA, 0x21, 0x10, 0xFF, 0xF3, 0xD2,<br>    0xCD, 0x0C, 0x13, 0xEC, 0x5F, 0x97, 0x44, 0x17, 0xC4, 0xA7, 0x7E, 0x3D, 0x64, 0x5D, 0x19, 0x73,<br>    0x60, 0x81, 0x4F, 0xDC, 0x22, 0x2A, 0x90, 0x88, 0x46, 0xEE, 0xB8, 0x14, 0xDE, 0x5E, 0x0B, 0xDB,<br>    0xE0, 0x32, 0x3A, 0x0A, 0x49, 0x06, 0x24, 0x5C, 0xC2, 0xD3, 0xAC, 0x62, 0x91, 0x95, 0xE4, 0x79,<br>    0xE7, 0xC8, 0x37, 0x6D, 0x8D, 0xD5, 0x4E, 0xA9, 0x6C, 0x56, 0xF4, 0xEA, 0x65, 0x7A, 0xAE, 0x08,<br>    0xBA, 0x78, 0x25, 0x2E, 0x1C, 0xA6, 0xB4, 0xC6, 0xE8, 0xDD, 0x74, 0x1F, 0x4B, 0xBD, 0x8B, 0x8A,<br>    0x70, 0x3E, 0xB5, 0x66, 0x48, 0x03, 0xF6, 0x0E, 0x61, 0x35, 0x57, 0xB9, 0x86, 0xC1, 0x1D, 0x9E,<br>    0xE1, 0xF8, 0x98, 0x11, 0x69, 0xD9, 0x8E, 0x94, 0x9B, 0x1E, 0x87, 0xE9, 0xCE, 0x55, 0x28, 0xDF,<br>    0x8C, 0xA1, 0x89, 0x0D, 0xBF, 0xE6, 0x42, 0x68, 0x41, 0x99, 0x2D, 0x0F, 0xB0, 0x54, 0xBB, 0x16,<br>)<br><br># Leaks one bit of information every operation<br>leak_buf = []<br>def leaky_aes_secret(data_byte, key_byte):<br>    out = Sbox[data_byte ^ key_byte]<br>    leak_buf.append(out &amp; 0x01)<br>    return out<br><br># Simplified version of AES with only a single encryption stage<br>def encrypt(plaintext, key):<br>    global leak_buf<br>    leak_buf = []<br>    ciphertext = [leaky_aes_secret(plaintext[i], key[i]) for i in range(16)]<br>    return ciphertext<br><br># Leak the number of 1 bits in the lowest bit of every SBox output<br>def encrypt_and_leak(plaintext):<br>    ciphertext = encrypt(plaintext, SECRET_KEY)<br>    ciphertext = None # throw away result<br>    time.sleep(0.01)<br>    return leak_buf.count(1)<br><br>pt = input(&quot;Please provide 16 bytes of plaintext encoded as hex: &quot;)<br>if len(pt) != 32:<br>    print(&quot;Invalid length&quot;)<br>    sys.exit(0)<br><br>pt = bytes.fromhex(pt)<br>print(&quot;leakage result:&quot;, encrypt_and_leak(pt))</pre><p>This code is written in Python3 and involves reading a secret key from a text file and using it to encrypt data.</p><p>The Sbox is a substitution table used for encryption. The “with open” statement reads the contents of the “key.txt” file, stripping any white space and converting the resulting string into bytes using the fromhex method.</p><p>The Sbox is a list of hexadecimal values that will be used for encryption. The code returns the numbers of the last bit obtained from the result of xorring the key with our supplied plaintext which returns a content from the SBOX and print it to us.</p><p>Connecting to the server we got this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*1QYoQWUDaoZcFpdsIdF0Wg.png" /></figure><p>connecting to the server using Netcat we got similar output as our assertion was correct, we could see that the output of our leakage result is 6 after supplying 16-byte of zero’s. Taking a peak at the hint it mentioned</p><blockquote>The “encryption” algorithm is simple and the correlation between the leakage and the key can be very easily modeled</blockquote><p>using this method i was able to write a<strong> </strong><a href="https://raw.githubusercontent.com/Cyberguru1/nokkers/master/_posts/files/power_analysis/warmup_sol.py"><strong>script</strong></a><strong> </strong>to find the possible key used</p><pre>leak_buf = []<br>out = []<br>full = []<br><br>flag = &#39;&#39;<br><br>for k in range(0, 16):<br>    out = []<br>    first,start = True, False<br>    checkk = False<br>    teach = True<br>    third = False<br>    prev = 0<br>    h = 0<br>    j = 0<br>    try:<br>        for i in range(0, 256+1):<br>            pt = hex(bytes_to_long(f&quot;{chr(i)}&quot;.encode()))[2:]<br>            pt = pt + &quot;00&quot;*(15 - k)<br>            pt = pt.zfill(32)<br>            val = encryp(pt)<br>            if val &gt; h:<br>                h = val<br>            if first:<br>                prev = val<br>            elif (start and teach):<br>                if val == prev:<br>                    c = hex(bytes_to_long(&#39;c&#39;.encode()))[2:]<br>                    c = c + &#39;00&#39;*13<br>                    c = c.zfill(32)<br>                    check = encryp(c)<br>                    out.extend([1, 1]) if check &lt;= val  else out.extend([0,0])<br>                elif val &gt; prev:<br>                    out.extend([0, 1])<br>                elif prev &gt; val:<br>                    out.extend([1, 0])<br>                start = False<br>                teach = False<br>            else:<br>                if val &gt; prev:<br>                    out.append(1)<br>                elif val == prev and (val == h):<br>                    out.append(1)<br>                else:<br>                    out.append(0)<br>            first = False<br>            start = True<br>            j += 1<br>            prev = val<br>        ind = list(mapping.values()).index(out)<br>        f = str(list(mapping.keys())[ind]).zfill(2)<br>        flag = flag + f<br>        print(&quot;Added: &quot;, f)<br>        print(&quot;+++++++++++++++++Flag:&quot;,flag)<br>        full.append(out)<br><br>    except:<br>        print(&quot;failed bit: &quot;)<br>        print(out)<br>        full.append(out)<br>        if out[0] == 0:<br>            out[0], out[1] = 1,1<br>        else:<br>            out[0], out[1] = 0,0<br>        try:<br>            ind = list(mapping.values()).index(out)<br>            flag = flag + list(mapping.keys())[ind]<br>        except:<br>            flag = flag +&#39;-&#39;<br>            continue<br><br>print(flag)<br>assert len(flag) == 32, &quot;not done&quot;<br>print(&quot;Flag bruteforced!!!!!!!!!!!!!!!!!!!!!!!!&quot;)</pre><p>yeah this is one of the most unpythonic script i have ever written but, it works</p><p><strong>Breakdown of the code:</strong></p><p>The code uses a for loop to iterate through 16 possible values of k. Within the loop, the code initializes several variables to their initial values, and then attempts to generate a string of binary digits that represents the output of an encryption function.</p><p>The code first generates a hex representation of the integer i, which ranges from 0 to 256. It then pads this hex representation with zeros so that it has a length of 32 characters. The resulting string is passed as input to the ‘encryp’ function, which generates an output value.</p><p>The code then checks the output value against several variables, including h, prev, start, teach, and first, to determine how to update the output binary string out. Depending on the values of these variables and the relationship between the current output value and the previous output value, the code appends either a 0 or a 1 to out.</p><p>Once the loop over i completes, the code tries to match the binary string out to a pre-defined dictionary called mapping. If a match is found, the corresponding key value is added to the flag string. If a match is not found, the code appends a “-” character to the flag string and continues to the next iteration of the loop over k.</p><p>After all 16 iterations over k complete, the final value of the flag string is printed to the console. If the length of the flag is not exactly 32 characters, an assertion error is raised. Otherwise, a success message is printed to the console ;).</p><p>and that’s how i was able to solve the warmup challenge if you enjoyed the writeup please give a clap or leave a comment</p><p>for more solution to Pico CTF 2023 challenges check out my personal <a href="http://vlog.cyb3rguru.tech/"><strong>vlog</strong></a><strong> </strong>here <a href="http://vlog.cyb3rguru.tech/">https://vlog.cyb3rguru.tech</a></p><p>Thanks for reading !!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf6bfe320a4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Postmortem]]></title>
            <link>https://medium.com/@hamzasaidu34/postmortem-c21c23ba2363?source=rss-cc0a164c9a4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c21c23ba2363</guid>
            <category><![CDATA[postmortem]]></category>
            <category><![CDATA[alx-blog]]></category>
            <category><![CDATA[servers]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[debugging]]></category>
            <dc:creator><![CDATA[Hamza Saidu]]></dc:creator>
            <pubDate>Fri, 10 Mar 2023 22:01:20 GMT</pubDate>
            <atom:updated>2023-03-10T22:01:20.537Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Postmortem</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*nerd_csN-zgbGtBRov2VAQ.jpeg" /></figure><p>Well, hello there! It’s me, cyberguru, and today we’re going to talk about the dreaded “p” word: post-mortem. I know, I know, it’s not the most exciting topic, but don’t worry, I’ve got some tricks up my sleeve to make it a little more interesting.</p><p>First off, let’s address the elephant in the room (or should I say, the skeleton in the closet?): a post-mortem is basically just a fancy way of saying “let’s figure out what went wrong.” And let’s be real, we’ve all been there. Whether it’s a failed project at work or a burnt batch of cookies in the kitchen, sometimes things just don’t go according to plan.</p><p>But fear not, my friends, because a post-mortem is actually a valuable tool for learning and improving. By analyzing what went wrong, we can make changes to prevent it from happening again in the future. And who doesn’t love a good “lessons learned” moment?</p><p>Now, I know what you’re thinking. But how can we make this post-mortem more exciting?” Well, how about we add a pretty diagram? Everyone loves a good visual aid, right?</p><p>Here’s a simple diagram I whipped up to help illustrate the post-mortem process:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*Wgflzf-AM9oStVZlRXjATg.png" /></figure><p>See? Easy peasy. Now, if that’s not enough to catch your attention, how about we add some real life scenario</p><p><strong>Issue Summary:</strong></p><p>On March 9, 2023, from 8:00 PM to 11:00 PM EST, the email service of our company experienced an outage, impacting 80% of our users. The root cause was a server failure due to a faulty hardware component.</p><p><strong>Timeline:</strong></p><p>* 8:00 PM: The issue was detected when several monitoring alerts were triggered indicating that the email service was not responding.</p><p>* 8:05 PM: Engineers investigated the email server and found that it was unresponsive.</p><p>* 8:10 PM: Assumption was made that the issue was due to a network connectivity problem and the network team was notified.</p><p>* 8:20 PM: The network team confirmed that there was no issue with the network connectivity.</p><p>* 8:30 PM: Investigation revealed that the server was not booting up due to a faulty hardware component.</p><p>* 8:35 PM: The faulty hardware component was identified as a failed hard drive.</p><p>* 9:00 PM: The incident was escalated to the senior engineering team for further investigation and resolution.</p><p>* 10:00 PM: The senior engineering team identified the root cause and started working on a solution.</p><p>* 11:00 PM: The email service was restored after replacing the faulty hard drive.</p><p><strong>Root Cause and Resolution:</strong></p><p>The root cause of the outage was a failed hard drive on the email server. The failed hard drive prevented the server from booting up and caused the email service to become unresponsive. The resolution to the issue was to replace the faulty hard drive and reboot the server.</p><p><strong>Corrective and Preventative Measures:</strong></p><p>To prevent such outages from happening again in the future, we will be implementing the following corrective and preventative measures:</p><p>* Implement a more robust hardware monitoring system to detect potential hardware failures before they occur.</p><p>* Implement redundant hardware components to reduce the risk of hardware failures causing service outages.</p><p>* Improve the incident escalation process to ensure timely resolution of issues.</p><p>* Develop a disaster recovery plan to minimize the impact of service outages.</p><p><strong>To address the issue at hand, the following tasks will be performed:</strong></p><p>* Replace the faulty hard drive on the email server.</p><p>* Conduct a full hardware inspection on all email servers to ensure no other faulty components are present.</p><p>* Update the hardware monitoring system to include more comprehensive monitoring and alerting features.</p><p>In conclusion, we understand the impact that this outage had on our users and we are taking steps to ensure that such incidents are minimized in the future. We appreciate the patience and understanding of our users during this time and will continue to provide high-quality service to the best of our abilities.</p><p>I hope you learned a little something about the value of post-mortems. So go forth, my friends, and embrace the process. Who knows, you might just save yourself from burning another batch of cookies.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c21c23ba2363" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>