<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on Muhammad Nuh</title><link>https://hexrogue.github.io/blog/</link><description>Recent content in Writing on Muhammad Nuh</description><generator>Hugo</generator><language>en-us</language><managingEditor>ikanlemas0@gmail.com (Muhammad Nuh)</managingEditor><webMaster>ikanlemas0@gmail.com (Muhammad Nuh)</webMaster><lastBuildDate>Sun, 25 Oct 2026 21:00:00 +0800</lastBuildDate><atom:link href="https://hexrogue.github.io/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Captain Learn Everything and the Line-by-Line Delusion</title><link>https://hexrogue.github.io/blog/captain-learn-everything-line-by-line-delusion/</link><pubDate>Sun, 25 Oct 2026 21:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/captain-learn-everything-line-by-line-delusion/</guid><description>&lt;p&gt;Someone told me, with the confidence of a person who has never been on call, that you need to learn everything. Not everything in your lane. Everything. Every language, every framework, every branch of engineering, every obscure protocol, presumably including the bit of JavaScript that makes the printer work and the ritual that keeps the build server alive.&lt;/p&gt;&#10;&lt;p&gt;I said no. You need the fundamentals, a map, and the willingness to go deep where it matters. They said no. Not &amp;ldquo;no, here is why.&amp;rdquo; Just no. The conversation equivalent of a popup with one button.&lt;/p&gt;</description></item><item><title>Emotional Immaturity Is Fear in a Trench Coat</title><link>https://hexrogue.github.io/blog/emotional-immaturity/</link><pubDate>Thu, 22 Oct 2026 12:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/emotional-immaturity/</guid><description>&lt;p&gt;Here is a thing I have done: turned a fifteen-minute delay in a text reply into a three-act tragedy, cast the other person as the villain, and called the performance &amp;ldquo;being honest.&amp;rdquo; Here is another: gone silent for two days because I was hurt, told myself I was protecting my peace, and made everyone else guess what they had done. I have also apologized with the word &amp;ldquo;but&amp;rdquo; so many times that the word should have its own chair at dinner.&lt;/p&gt;</description></item><item><title>You Clicked "Accept All." Here's What You Just Agreed To.</title><link>https://hexrogue.github.io/blog/cookies-trackers-consent-banner/</link><pubDate>Thu, 22 Oct 2026 10:30:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/cookies-trackers-consent-banner/</guid><description>&lt;p&gt;Somewhere on the page, a banner is waiting. It has two buttons. One says Accept All. The other says Manage Preferences, which is less a button than a threat with a font and a legal department.&lt;/p&gt;&#10;&lt;p&gt;You click Accept All because you want to read the article. You have now agreed to a data-processing arrangement involving companies you have never heard of, in countries you cannot point to on a map, for purposes described in a document written by someone paid by the word. The document is longer than the article. It is longer than the article&amp;rsquo;s source code. It may be longer than your attention span, which is currently being held together by caffeine and a deep-fried burrito with a death wish.&lt;/p&gt;</description></item><item><title>Turnitin Flagged 19 Sentences. I Flagged Its Homework.</title><link>https://hexrogue.github.io/blog/turnitin-highlighted-19-sentences/</link><pubDate>Wed, 21 Oct 2026 09:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/turnitin-highlighted-19-sentences/</guid><description>&lt;p&gt;Twenty-two pages. Four thousand and forty-one words. A PDF opens and the introduction looks like someone lost a fight with a blue highlighter.&lt;/p&gt;&#10;&lt;p&gt;At the top, in the kind of font that expects to be taken seriously: 26% detected as AI. Nineteen blue chunks. That&amp;rsquo;s it? That&amp;rsquo;s the evidence? I have seen more rigorous accusations from a fortune cookie.&lt;/p&gt;&#10;&lt;p&gt;Turnitin: I also have a disclaimer.&lt;/p&gt;&#10;&lt;p&gt;Me: Of course you do.&lt;/p&gt;</description></item><item><title>Mastery Is 80%</title><link>https://hexrogue.github.io/blog/mastery-is-eighty-percent/</link><pubDate>Tue, 20 Oct 2026 09:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/mastery-is-eighty-percent/</guid><description>&lt;p&gt;Fifteen out of twenty. For a program that reads a number and prints a grade.&lt;/p&gt;&#10;&lt;p&gt;Somewhere, a marker looked at a two-option rubric and picked a third. We will get to that.&lt;/p&gt;&#10;&lt;p&gt;The brief: read a score from 0 to 100, print the alphabetical grade and the description, print an error message if the input is out of range. I have been paid to write code for six years. Twenty minutes, including the screenshot.&lt;/p&gt;</description></item><item><title>RSSI is a liar</title><link>https://hexrogue.github.io/blog/rssi-dbm-noise-floor/</link><pubDate>Mon, 05 Oct 2026 09:45:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/rssi-dbm-noise-floor/</guid><description>&lt;p&gt;Your laptop reports -67 dBm and streams video. Your phone reports -67 dBm and stutters. Neither number is lying about the signal. Both are lying about the quality, because the signal alone does not contain the noise. RSSI is the friend who says &amp;ldquo;I&amp;rsquo;m five minutes away&amp;rdquo; from another city.&lt;/p&gt;&#10;&lt;h2 id="dbm-is-a-log-scale"&gt;dBm is a log scale&lt;/h2&gt;&#10;&lt;p&gt;0 dBm is one milliwatt. Every 3 dB doubles or halves the power, and every 10 dB is a factor of ten. So -60 dBm is ten times the power of -70 dBm, and -70 is ten times -80. The gap between &amp;ldquo;fine&amp;rdquo; and &amp;ldquo;dead&amp;rdquo; is smaller than the numbers suggest: -67 to -80 is 13 dB, roughly a factor of twenty in power.&lt;/p&gt;</description></item><item><title>Decrypting your own WPA2 traffic in Wireshark</title><link>https://hexrogue.github.io/blog/decrypt-wpa2-traffic-wireshark/</link><pubDate>Fri, 11 Sep 2026 20:10:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/decrypt-wpa2-traffic-wireshark/</guid><description>&lt;p&gt;A monitor mode capture is mostly noise: beacons, management frames, and encrypted data you cannot read. It is the digital equivalent of taping a conversation through a wall and getting a very detailed recording of the wall.&lt;/p&gt;&#10;&lt;p&gt;Wireshark will decrypt your own WPA2 traffic if you give it the passphrase and the capture contains the handshake. Miss either one and you have a very expensive screensaver. The gap between those two conditions is where most people get stuck.&lt;/p&gt;</description></item><item><title>Building the ESP32 recon rig for real</title><link>https://hexrogue.github.io/blog/esp32-recon-rig-build-guide/</link><pubDate>Fri, 28 Aug 2026 14:55:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/esp32-recon-rig-build-guide/</guid><description>&lt;p&gt;The driver post was about the kernel refusing to let the board talk. This one is the build: what to buy, how it is wired, how it flashes, and the things that wasted an evening. It is the IKEA instruction manual of wifi hardware, except the allen key is a USB cable and the missing screw is your evening. It is written for a board pointed at your own network, and the rules for that are on &lt;a href="https://hexrogue.github.io/lab-rules/"&gt;the lab rules&lt;/a&gt; page.&lt;/p&gt;</description></item><item><title>The 2.4 GHz food fight</title><link>https://hexrogue.github.io/blog/24ghz-interference-channel-planning/</link><pubDate>Fri, 07 Aug 2026 08:30:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/24ghz-interference-channel-planning/</guid><description>&lt;p&gt;Your wifi is fine at 8am and unusable at 8pm. Nothing in your house changed. The band did. 2.4 GHz is shared with microwaves, Bluetooth, cordless phones, baby monitors, Zigbee and every neighbour&amp;rsquo;s router, and it has three usable lanes.&lt;/p&gt;&#10;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/memes/meme-24ghz-crowded.jpg" alt="This Is Fine dog meme: 2.4 GHz at 8 PM while the microwave, Bluetooth, a baby monitor, and 37 neighbours all share the band"&gt;&#10;&lt;figcaption&gt;The band is not crowded. It is a group project where everyone brought a microwave.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;h2 id="three-lanes-thirteen-labels"&gt;Three lanes, thirteen labels&lt;/h2&gt;&#10;&lt;p&gt;The band runs from 2.400 to 2.4835 GHz. Channels are numbered 5 MHz apart, but a 20 MHz wifi channel occupies four of those gaps. That is why 1, 6 and 11 are the only non-overlapping choices in the common plan: each takes a 20 MHz slice, and they just touch at the edges.&lt;/p&gt;</description></item><item><title>WPA3 SAE, without the fairy tales</title><link>https://hexrogue.github.io/blog/wpa3-sae-dragonfly-handshake/</link><pubDate>Sat, 01 Aug 2026 17:40:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/wpa3-sae-dragonfly-handshake/</guid><description>&lt;p&gt;WPA3 has a reputation problem. Marketing calls it unhackable, forums call it broken, and both are wrong in useful ways. The honest version is narrower and more interesting: WPA3 kills the offline dictionary attack, which is the technique most people mean when they say their wifi got hacked.&lt;/p&gt;&#10;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/memes/meme-wpa3-fine.jpg" alt="This Is Fine dog meme: WPA3 is unhackable while transition mode quietly keeps WPA2 alive"&gt;&#10;&lt;figcaption&gt;Marketing says unhackable. Transition mode says hold my WPA2.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;h2 id="the-thing-sae-removes"&gt;The thing SAE removes&lt;/h2&gt;&#10;&lt;p&gt;Start with what WPA2 gives an attacker. The passphrase becomes a key, the four-way handshake derives session keys, and the whole exchange is readable on the air. A recording contains everything needed to test guesses at home, at full speed, on a machine that never has to touch the network again. The cracker is not attacking your router. They are attacking a file.&lt;/p&gt;</description></item><item><title>Why your phone clings to a dead wifi access point</title><link>https://hexrogue.github.io/blog/wifi-roaming-sticky-clients/</link><pubDate>Wed, 15 Jul 2026 10:25:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/wifi-roaming-sticky-clients/</guid><description>&lt;p&gt;Walk from the kitchen to the bedroom on a call. The phone still shows two bars, still names the access point you left behind, and the voice turns to gravel. You did not lose wifi. Your phone chose to keep it.&lt;/p&gt;&#10;&lt;p&gt;That choice is the whole story of roaming, and it is the one part of wifi people assume the network controls. It does not. The standard gives the client the vote, and the access point gets a suggestion box.&lt;/p&gt;</description></item><item><title>How a captive portal works, and how to build one on an ESP</title><link>https://hexrogue.github.io/blog/esp-captive-portal-explained/</link><pubDate>Fri, 03 Jul 2026 21:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/esp-captive-portal-explained/</guid><description>&lt;p&gt;Join a hotel wifi, and before you type anything, your phone opens a login page. Nothing is installed and nobody told you to look, yet the page appears. It is the digital equivalent of a hotel clerk sliding a form under the door before you have taken off your shoes. Two old tricks stacked on each other put it there, and both are small enough to run on the ESP32 on my desk.&lt;/p&gt;</description></item><item><title>BLE past advertising: GATT, bonding and why trackers work</title><link>https://hexrogue.github.io/blog/ble-beyond-advertising-gatt-and-trackers/</link><pubDate>Mon, 08 Jun 2026 13:35:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/ble-beyond-advertising-gatt-and-trackers/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/passive-recon-wifi-and-ble/"&gt;The recon post&lt;/a&gt; stops where most Bluetooth writing stops: a device shouts small packets into the room and you write down its name and address. That is advertising, and it is the shallow half. The other half is what happens once two devices agree to talk.&lt;/p&gt;&#10;&lt;p&gt;Bluetooth is a toddler with a walkie-talkie. Advertising is the part where it shouts its name. GATT is the part where it hands you a three-ring binder and expects you to admire the tabs.&lt;/p&gt;</description></item><item><title>Sub-GHz primer: 433 MHz, weather stations and remote controls</title><link>https://hexrogue.github.io/blog/sub-ghz-primer-433mhz/</link><pubDate>Sun, 31 May 2026 15:20:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/sub-ghz-primer-433mhz/</guid><description>&lt;p&gt;Wifi and Bluetooth both live at 2.4 GHz. The rest of the cheap wireless world lives below 1 GHz, and the ESP32 cannot hear any of it. That is the entire reason the second half of this project exists, and the reason your cheap remote control can reach the garage while your phone gives up at the kitchen door. The setup deserves a primer before the hardware arrives.&lt;/p&gt;&#10;&lt;h2 id="why-below-1-ghz"&gt;Why below 1 GHz&lt;/h2&gt;&#10;&lt;p&gt;Lower frequencies go further and through more walls at the same power. A 433 MHz signal from a coin cell crosses a house; a 2.4 GHz signal from the same cell struggles with two walls. The trade is bandwidth, and these devices do not need bandwidth. A weather sensor sends twelve bytes every minute. A doorbell sends one bit when pressed. A lower frequency with a wide open band is the correct engineering choice, and it has been for thirty years.&lt;/p&gt;</description></item><item><title>Beacon spam: how the air fills with junk network names</title><link>https://hexrogue.github.io/blog/beacon-spam-and-the-wifi-list/</link><pubDate>Tue, 12 May 2026 09:05:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/beacon-spam-and-the-wifi-list/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/80211-frames-you-can-read/"&gt;A beacon&lt;/a&gt; is the simplest frame in wifi. A router announces its name about ten times a second, on its channel, to nobody in particular. It is unsigned, it is unencrypted, and any radio can transmit one.&lt;/p&gt;&#10;&lt;p&gt;Your phone treats that announcement like a guest list. No bouncer, no ID check, no guy named Chad at the door asking if you are on the list. Anyone with a radio can add a name. Copy that frame at scale and you have beacon spam.&lt;/p&gt;</description></item><item><title>Cracking your own password: from PMKID to hashcat</title><link>https://hexrogue.github.io/blog/cracking-your-own-password-pmkid/</link><pubDate>Wed, 29 Apr 2026 19:45:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/cracking-your-own-password-pmkid/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/80211-frames-you-can-read/"&gt;The PMKID is a coat-check ticket&lt;/a&gt;: a blob the router hands out before any real authentication, derived from your wifi passphrase. This post is the other half, the part where the ticket becomes a password. On your own network, in your own lab, which is the only version of this that belongs on a blog. It is also the closest thing wifi has to a receipt that says &amp;ldquo;your password is probably fine, but let&amp;rsquo;s check.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Watching your own air: rogue access points and evil twins</title><link>https://hexrogue.github.io/blog/watching-your-own-air-rogue-aps/</link><pubDate>Tue, 07 Apr 2026 11:10:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/watching-your-own-air-rogue-aps/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/passive-recon-wifi-and-ble/"&gt;Recon&lt;/a&gt; gives you a table of every radio in range. This post is about the one entry that should not be there.&lt;/p&gt;&#10;&lt;p&gt;It is the wifi equivalent of finding a second front door on your house, with a welcome mat that has your name on it.&lt;/p&gt;&#10;&lt;p&gt;A rogue access point is any access point that is not part of your inventory. There are two shapes of it. The boring one is a real access point, plugged into your network, that nobody documented, usually a spare router someone enabled because the wifi was slow. The interesting one is not on your network at all: it is a second radio wearing your network&amp;rsquo;s name, broadcasting to your devices, waiting for them to join it.&lt;/p&gt;</description></item><item><title>WPA2, WPA3 and PMF: what actually stops the attacks I wrote about</title><link>https://hexrogue.github.io/blog/wpa2-wpa3-pmf-what-stops-them/</link><pubDate>Tue, 31 Mar 2026 16:30:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/wpa2-wpa3-pmf-what-stops-them/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/deauth-frames-anyone-can-forge/"&gt;The deauth post&lt;/a&gt; ends with a promise: the fix is management frame protection, and modern gear just ignores a forged eviction notice. That is the short version. The long version is that wifi security has two generations, and the reason half the networks you can see are still forged-frame food is a compatibility setting. This post is the part where the promise meets the router menu, and the router menu is a swamp.&lt;/p&gt;</description></item><item><title>Passive recon: what a listener learns without joining anything</title><link>https://hexrogue.github.io/blog/passive-recon-wifi-and-ble/</link><pubDate>Sun, 15 Mar 2026 08:50:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/passive-recon-wifi-and-ble/</guid><description>&lt;p&gt;Your phone&amp;rsquo;s wifi chip has opinions. It only hands the operating system frames addressed to it or to the network it belongs to, and it drops the rest without ceremony. It is the digital equivalent of a bouncer who only lets in people on the list, and then someone shows up with a clipboard and a monitor-mode adapter. Promiscuous mode turns that filter off and keeps everything the radio can hear.&lt;/p&gt;</description></item><item><title>Deauth: the 26 bytes anyone can forge</title><link>https://hexrogue.github.io/blog/deauth-frames-anyone-can-forge/</link><pubDate>Fri, 06 Mar 2026 20:15:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/deauth-frames-anyone-can-forge/</guid><description>&lt;p&gt;A deauth frame is a wifi eviction notice. It says one thing: you are no longer associated with this network. Twenty-six bytes that prove nothing about who sent them.&lt;/p&gt;&#10;&lt;p&gt;That missing proof is the entire story. It is the bureaucratic version of a bouncer throwing you out and then handing you a form that says &amp;ldquo;we have no idea who did this.&amp;rdquo;&lt;/p&gt;&#10;&lt;h2 id="the-frame"&gt;The frame&lt;/h2&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;c0 00 &amp;lt;- frame control: management frame, subtype 12 (deauth)&#10;3a 01 &amp;lt;- duration, filler, ignored&#10;ff:ff:ff:ff:ff:ff &amp;lt;- address 1: the target. broadcast means everyone listening&#10;02:11:22:33:44:55 &amp;lt;- address 2: who sent it (supposed to be the access point)&#10;02:11:22:33:44:55 &amp;lt;- address 3: which network this concerns&#10;f0 ff &amp;lt;- sequence number&#10;02 00 &amp;lt;- reason code 2: previous authentication no longer valid&#10;&lt;/code&gt;&lt;/pre&gt;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/diagrams/deauth-frame-layout.svg" alt="Byte by byte layout of the 26 byte deauthentication frame"&gt;&#10;&lt;figcaption&gt;The whole 26 bytes, laid out. Six of them hold the sender's address, and none of them are proof that the sender is who they claim.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;The first byte pair &lt;code&gt;c0 00&lt;/code&gt; is the giveaway. The top bits of &lt;code&gt;0xc0&lt;/code&gt; say management frame, the rest say subtype 12. Disassociation is the sibling, subtype 10, byte &lt;code&gt;a0&lt;/code&gt;. Over the air the two look nearly identical and are used the same way.&lt;/p&gt;</description></item><item><title>802.11 frames you can read straight off the air</title><link>https://hexrogue.github.io/blog/80211-frames-you-can-read/</link><pubDate>Tue, 10 Feb 2026 10:40:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/80211-frames-you-can-read/</guid><description>&lt;p&gt;Every wifi packet you will ever capture is the same envelope. Once that clicks, a wall of hex becomes a conversation you can follow with one eye. The first time it clicks, you feel like a wizard. The second time, you realize the wizard is just reading headers and taking notes.&lt;/p&gt;&#10;&lt;h2 id="the-envelope"&gt;The envelope&lt;/h2&gt;&#10;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/esp32/80211-mac-frame.svg" alt="802.11 MAC frame layout: frame control, duration, three addresses, sequence control, frame body and FCS"&gt;&#10;&lt;figcaption&gt;The 802.11 MAC frame. Diagram by Superspritz, CC BY-SA 4.0, via Wikimedia Commons.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;The first two bytes are frame control. They answer the two questions that matter: what type of frame is this, and what flavour of that type. Two bits say management, control or data. Four more say the subtype, so a beacon is a management frame of subtype 8, a deauth is management subtype 12, an ACK is control subtype 13.&lt;/p&gt;</description></item><item><title>WiFi in plain words: access points, stations, and the join dance</title><link>https://hexrogue.github.io/blog/wifi-ap-sta-how-devices-join/</link><pubDate>Fri, 30 Jan 2026 14:05:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/wifi-ap-sta-how-devices-join/</guid><description>&lt;p&gt;A wifi network is not a thing you connect to. It is one device that decided to be a landlord, plus every device that agreed to rent. The landlord sends a name tag ten times a second and calls it customer service.&lt;/p&gt;&#10;&lt;p&gt;The landlord is the access point, or AP. It holds the network name, sets the rules, and bridges the air to the wired side of the world. The tenants are stations, or STA. Your phone is a station. Your laptop is a station. The TV, the printer, and the ESP32 on my desk are stations. In most homes the AP and the router are the same plastic box, which is why everyone uses the two words for one thing.&lt;/p&gt;</description></item><item><title>I Taught a $5 Board to Sniff WiFi, Then Fought Its Driver</title><link>https://hexrogue.github.io/blog/esp32-recon-rig-driver-said-no/</link><pubDate>Mon, 12 Jan 2026 09:20:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/esp32-recon-rig-driver-said-no/</guid><description>&lt;p&gt;It started with an ESP32 plugged into my laptop and a simple question: what can this thing actually hear. It ended one long evening later with me disassembling a closed WiFi driver, downgrading an entire SDK for nothing, and learning more about 802.11 frames than any lecture ever taught me. The answer was &amp;ldquo;more than the driver wanted me to know,&amp;rdquo; which is how a five-dollar board turns into a vendetta. The board now runs a recon dashboard I built from scratch. This is the whole story, including the part where I was wrong in public.&lt;/p&gt;</description></item><item><title>The Uniform Is Not a Personality</title><link>https://hexrogue.github.io/blog/malaysian-police-reality/</link><pubDate>Wed, 10 Dec 2025 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/malaysian-police-reality/</guid><description>&lt;p&gt;First, the disclaimer so nobody burns my house down. Some cops are good. Professional, calm, do the paperwork, go home. This post is not about them. If you are a good cop, you already know exactly which colleagues this is about. Everyone else, pull up a chair.&lt;/p&gt;&#10;&lt;p&gt;Second, the scope. This post is about the criminal investigation and narcotics side: lockups, interrogation rooms, remand games, confession farming. The traffic officer writing fines is a different beast with smaller teeth. A few roadside bits appear because the same culture leaks everywhere, but fines cost money and cells cost years. The cells are the point.&lt;/p&gt;</description></item><item><title>I Pointed Shodan at My Own IP</title><link>https://hexrogue.github.io/blog/i-pointed-shodan-at-my-own-ip/</link><pubDate>Thu, 14 Aug 2025 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/i-pointed-shodan-at-my-own-ip/</guid><description>&lt;p&gt;Last month I searched for myself on the internet. Not my name. My IP address. What came back was a list of my open doors, written up neatly like a menu. It was the digital equivalent of finding your house listed on a tour guide, with photos of the unlocked windows. I had published myself and never noticed.&lt;/p&gt;&#10;&lt;h2 id="shodan-is-google-for-machines"&gt;Shodan is Google for machines&lt;/h2&gt;&#10;&lt;p&gt;Google indexes websites. Shodan indexes everything else: routers, cameras, servers, smart fridges with opinions. It knocks on every door on the internet, writes down who answers and what they say about themselves, and puts it in a search bar.&lt;/p&gt;</description></item><item><title>Thinking About Marriage</title><link>https://hexrogue.github.io/blog/thinking-about-marriage/</link><pubDate>Sat, 21 Jun 2025 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/thinking-about-marriage/</guid><description>&lt;p&gt;I did not want to write this. I do not tell people my feelings. I feel ashamed even trying, like I am opening a door that should stay closed. But some things sit in the chest too long and start to ache, and this is one of them. So I am putting it here, for me. I doubt anyone will ever read this. Maybe years from now, an older me will find this page again and remember the nights he sat alone wondering. If he is the only reader this ever gets, that is enough.&lt;/p&gt;</description></item><item><title>What Your Smart TV Says at 3 AM</title><link>https://hexrogue.github.io/blog/wireshark-tips-read-your-network/</link><pubDate>Mon, 28 Apr 2025 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/wireshark-tips-read-your-network/</guid><description>&lt;p&gt;Wireshark does not ease you in. My first capture was a wall of packets, and I understood zero of them. It looked like a spreadsheet had a panic attack. Three filters later, it looked like a spreadsheet with a therapist. The panic turned into a reading list.&lt;/p&gt;&#10;&lt;p&gt;I wish someone had handed me this version on day one.&lt;/p&gt;&#10;&lt;h2 id="capture-everything-then-filter-like-you-mean-it"&gt;Capture everything, then filter like you mean it&lt;/h2&gt;&#10;&lt;p&gt;Start a capture on your WiFi interface and you will see hundreds of packets per second. Do not read them. You would be drinking from a firehose. Learn three filters on day one. &lt;code&gt;ip.addr == x.x.x.x&lt;/code&gt; shows one device. &lt;code&gt;dns&lt;/code&gt; shows name lookups. &lt;code&gt;http&lt;/code&gt; shows unencrypted web traffic. Ninety percent of beginner questions die to one of these three.&lt;/p&gt;</description></item><item><title>Do It Scared</title><link>https://hexrogue.github.io/blog/do-it-scared/</link><pubDate>Sun, 09 Mar 2025 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/do-it-scared/</guid><description>&lt;p&gt;I overthink everything. Small things get ten rehearsals in my head before I open my mouth. Big things get a full headcount of who will stand against me. Most days fear runs the meeting and I just sit there taking notes.&lt;/p&gt;&#10;&lt;p&gt;Took me years to get this one thing. The fear never leaves first. You do not wait until you feel brave and then act. You act while your hands shake. Nobody is brave. Everyone is afraid of something. Some people just move anyway.&lt;/p&gt;</description></item><item><title>Ego Is Expensive, I Paid Mine in Full</title><link>https://hexrogue.github.io/blog/ego-is-expensive/</link><pubDate>Wed, 15 Jan 2025 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/ego-is-expensive/</guid><description>&lt;p&gt;I have a big ego. Not past tense. I do not apologize. I do not admit mistakes. When something bothers me, I go cold and wait for the person to notice. I wait for them to feel guilty. That is the pattern, written plain.&lt;/p&gt;&#10;&lt;p&gt;It feels like control. It is not. It is immature, and I finally see it because I keep paying for it. A friendship that went cold because neither of us would send the first message. A work argument I &amp;ldquo;won&amp;rdquo; and then sat with the damage for a month. Small cuts, every time. Ego rarely burns your life in one fire. It takes small cuts until the room is emptier.&lt;/p&gt;</description></item><item><title>Will AI Replace Us? Nah, But It Will Expose Us</title><link>https://hexrogue.github.io/blog/will-ai-replace-us/</link><pubDate>Tue, 26 Nov 2024 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/will-ai-replace-us/</guid><description>&lt;p&gt;Ngl, I am tired of this question. Every family gathering now: &amp;ldquo;Nuh, AI can code already right? So programmers habis la?&amp;rdquo; Bro. Chill. I have heard this question more times than I have heard my own name at dinner. And I love my family. Mostly.&lt;/p&gt;&#10;&lt;p&gt;Yes, I use AI daily. Yes, it writes half my boilerplate. No, it has not replaced me. It just made the boring parts faster and the dumb parts more obvious.&lt;/p&gt;</description></item><item><title>My Bank Locked Me Out for Typing Like a Human</title><link>https://hexrogue.github.io/blog/malaysian-banks-locked-me-out/</link><pubDate>Tue, 17 Sep 2024 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/malaysian-banks-locked-me-out/</guid><description>&lt;p&gt;Let me say this first so nobody gets confused. Malaysia is great. Food is elite, Grab shows up in four minutes, my MyKad renews faster than most countries ship a parcel. Then there is online banking, which feels designed by someone who has never forgotten a password in their life.&lt;/p&gt;&#10;&lt;p&gt;I use a password manager. I am the good user, the exact person every security blog begs you to become. Last Tuesday I tried to pay a bill at 11 PM. The manager filled in a 20 character monster, I reached for Enter, and my finger landed on the backslash key sitting right next to it. Tried again. Backslash. Third time, same key, because at 11 PM my hand runs on autopilot. Three wrong tries. Account blocked. Not slowed down. Blocked. My reward for doing security correctly was getting locked out over a key that lives one centimeter from Enter.&lt;/p&gt;</description></item><item><title>I Deleted Ads at the DNS Level</title><link>https://hexrogue.github.io/blog/dns-level-ad-blocking/</link><pubDate>Mon, 08 Jul 2024 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/dns-level-ad-blocking/</guid><description>&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/green-hills.jpg" alt="What the internet looks like with DNS filtering"&gt;&#10;&lt;figcaption&gt;What the internet looks like with DNS filtering. Probably.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;Last time I caught my TV phoning home at 3 AM. Readers asked what I did after the VLAN. The answer: I stopped the calls from leaving the house at all. Not with an ad blocker in the browser. With a bouncer at the DNS. The bouncer is a text file and a bad attitude.&lt;/p&gt;</description></item><item><title>The One-Number Bug That Leaked Orders</title><link>https://hexrogue.github.io/blog/idor-everyones-orders/</link><pubDate>Mon, 20 May 2024 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/idor-everyones-orders/</guid><description>&lt;p&gt;Some bugs crash your app. The scary ones politely hand you other people&amp;rsquo;s data. I found one of those in a test shop, and it took changing a single number. One number. No exploit kit, no hoodie, no dramatic typing. Just a URL with the confidence of a bad password.&lt;/p&gt;&#10;&lt;h2 id="what-is-an-idor-explained-with-lockers"&gt;What is an IDOR, explained with lockers&lt;/h2&gt;&#10;&lt;p&gt;Imagine school lockers. Yours is number 42. You ask the office &amp;ldquo;what is in locker 42&amp;rdquo; and they tell you. Now imagine you ask &amp;ldquo;what is in locker 43&amp;rdquo; and they tell you that too, no questions asked. That is an IDOR: a bug where the app checks who you are, but never checks whether the thing you asked for is yours.&lt;/p&gt;</description></item><item><title>Teaching a Server to Answer Calls</title><link>https://hexrogue.github.io/blog/teaching-server-answer-calls/</link><pubDate>Tue, 05 Mar 2024 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/teaching-server-answer-calls/</guid><description>&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/coffee-beans.jpg" alt="Debugging fuel"&gt;&#10;&lt;figcaption&gt;Debugging fuel. Consumed in large quantities during this project.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;My admissions CRM could text people automatically. Then the boss asked the obvious question: can it call them too? That question cost me a month and taught me more about real time systems than anything before it. It also cost me my sleep schedule, which was already on a payment plan. This is that month.&lt;/p&gt;&#10;&lt;h2 id="the-gap-between-texting-and-talking"&gt;The gap between texting and talking&lt;/h2&gt;&#10;&lt;p&gt;Texting through code is posting letters. Your program hands words to a server, the server delivers them whenever. Nothing has to be alive at the same time. I had that working in days.&lt;/p&gt;</description></item><item><title>How I taught Go to make phone calls</title><link>https://hexrogue.github.io/blog/go-phone-calls-whatsapi/</link><pubDate>Sun, 11 Feb 2024 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/go-phone-calls-whatsapi/</guid><description>&lt;p&gt;Texting through code is easy. Your program sends words, the other side receives words. Done. Then someone asks &amp;ldquo;can it also call people&amp;rdquo; and you discover that voice is a whole different animal. This is the story of teaching my Go gateway to speak.&lt;/p&gt;&#10;&lt;h2 id="messages-are-letters-calls-are-conversations"&gt;Messages are letters, calls are conversations&lt;/h2&gt;&#10;&lt;p&gt;Think of a text message like a letter. You write it, you post it, it arrives whenever. Nothing needs to be live at the same time. A phone call is a conversation: both sides talking at once, reacting instantly, and if the words arrive late or jumbled, the whole thing falls apart.&lt;/p&gt;</description></item><item><title>My TV Was Spying on Me</title><link>https://hexrogue.github.io/blog/my-tv-spying-homelab/</link><pubDate>Mon, 09 Oct 2023 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/my-tv-spying-homelab/</guid><description>&lt;p&gt;I bought a used router to flash OpenWrt on a bored Saturday. The plan was simple: better WiFi. Three weeks later I had VLANs, WireGuard back home, and a spreadsheet of every domain my TV talks to at 3 AM. The spreadsheet was not part of the plan. The spreadsheet is never part of the plan. This is how that happens. Nobody plans a homelab. It accretes.&lt;/p&gt;&#10;&lt;h2 id="it-started-with-one-vlan"&gt;It started with one VLAN&lt;/h2&gt;&#10;&lt;p&gt;The TV was the trigger. It wanted internet for Netflix and nothing else, but it knocked on telemetry endpoints all night. So it got its own VLAN with no access to the rest of the LAN, DNS forced through my filter, and inter-VLAN routing denied by default.&lt;/p&gt;</description></item><item><title>Arch Broke, and I Am Glad</title><link>https://hexrogue.github.io/blog/arch-broke-and-im-glad/</link><pubDate>Tue, 22 Aug 2023 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/arch-broke-and-im-glad/</guid><description>&lt;p&gt;Yes, Arch is my daily driver. No, I will not shut up about it. But this is not a conversion post. This is about the Tuesday an update left me staring at a boot menu with no Arch in it, and why I am glad it happened. The boot menu is a polite way of saying the computer has decided to take a personal day.&lt;/p&gt;&#10;&lt;h2 id="the-update-that-removed-my-os-from-the-menu"&gt;The update that removed my OS (from the menu)&lt;/h2&gt;&#10;&lt;p&gt;Pacman did its thing, I rebooted, and the bootloader offered me exactly one option: the fallback that also did not work. My root partition was fine. My kernel was fine. The boot entry was just gone. Somewhere between the kernel package and my EFI partition, a path disagreed with another path.&lt;/p&gt;</description></item><item><title>Fission and Fusion, Explained Like You Are Five</title><link>https://hexrogue.github.io/blog/fission-vs-fusion/</link><pubDate>Tue, 01 Aug 2023 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/fission-vs-fusion/</guid><description>&lt;p&gt;The sun is a fusion bomb that never stops exploding, held together by its own weight. Humans learned to split atoms before we understood them, and we are still learning to squeeze them. It is the universe&amp;rsquo;s oldest power plant, and we are still reading the manual with a flashlight. This is the story of both, no physics degree needed.&lt;/p&gt;&#10;&lt;h2 id="mass-is-frozen-energy"&gt;Mass is frozen energy&lt;/h2&gt;&#10;&lt;p&gt;Einstein&amp;rsquo;s famous equation says mass and energy are the same stuff in different outfits. Mass is energy standing still. A paperclip holds enough frozen energy to power a city, if you could thaw all of it. Nuclear reactions thaw a slice of it. Burning coal only rearranges the outfits. Nuclear reactions change the actors. That is why a kilogram of uranium outruns tons of coal. It is not a better fire. It is different bookkeeping.&lt;/p&gt;</description></item><item><title>Arch Linux Tips: Survive and Enjoy</title><link>https://hexrogue.github.io/blog/arch-tips-survive-and-enjoy/</link><pubDate>Wed, 14 Jun 2023 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/arch-tips-survive-and-enjoy/</guid><description>&lt;p&gt;Arch has a reputation for breaking. Mine breaks about twice a year, takes twenty minutes to fix, and teaches me something each time. The secret is not skill. It is habits, all of them boring, most of them learned while staring at a black screen and pretending the silence is a feature.&lt;/p&gt;&#10;&lt;h2 id="tip-one-read-before-you-press-y"&gt;Tip one: read before you press Y&lt;/h2&gt;&#10;&lt;p&gt;Pacman tells you exactly what it is about to do. Read it. Version jumps on kernels, drivers, and bootloaders deserve a glance at the Arch news feed first. Major changes get announced there with manual steps attached. Five minutes of reading prevents ninety percent of breakage. The updates can wait until after coffee.&lt;/p&gt;</description></item><item><title>Your Prayer App Downloads the Answer. I Derived It.</title><link>https://hexrogue.github.io/blog/my-go-prayer-time-calculator-from-pdf-formulas-to-terminal-tui/</link><pubDate>Sun, 07 May 2023 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/my-go-prayer-time-calculator-from-pdf-formulas-to-terminal-tui/</guid><description>&lt;p&gt;I found a paper called &amp;ldquo;Tracing the Shadow: Mathematical Calculation of Prayer Times Using Spherical Trigonometry.&amp;rdquo; The title alone had enough syllables to scare off a normal person, which is exactly how I knew I had to read it. I read it anyway.&lt;/p&gt;&#10;&lt;p&gt;I wanted to know how the app on my phone knew. Most apps download the answer from a server. Nobody shows the work. So I opened the paper and started translating it into Go.&lt;/p&gt;</description></item><item><title>A Four-Evening Crackme</title><link>https://hexrogue.github.io/blog/crackme-four-evenings/</link><pubDate>Mon, 27 Mar 2023 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/crackme-four-evenings/</guid><description>&lt;p&gt;After years of CTFs, a tiny crackme that asks for a serial key should have been a one evening job. A friend sent it over and said it would take an hour. It took four. The friend was right about the hour. The other three were a personal problem.&lt;/p&gt;&#10;&lt;h2 id="evening-one-strings-and-false-confidence"&gt;Evening one: strings and false confidence&lt;/h2&gt;&#10;&lt;p&gt;I ran strings on it and found the success message in plain text. I felt like a genius for about ten minutes. Then I opened it in Ghidra and the decompiler gave me a wall of FUN_00101060. Years of experience, same first reaction every time. My confidence filed for divorce.&lt;/p&gt;</description></item><item><title>Everything in My First Binary Was Named FUN_00101060</title><link>https://hexrogue.github.io/blog/reversing-tips-beginners/</link><pubDate>Thu, 19 Jan 2023 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/reversing-tips-beginners/</guid><description>&lt;p&gt;The first binary I opened looked like a city with no street signs. Ghidra handed me a map full of FUN_00101060 and expected me to navigate. The map was technically correct. So is a phone book with no names. I did what every beginner does: stared at it, changed nothing, and closed the laptop.&lt;/p&gt;&#10;&lt;p&gt;A few binaries later, I have a loop that works.&lt;/p&gt;&#10;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/diagrams/reversing-workflow.svg" alt="Diagram of the reversing loop: run strings, rename what you understand, then let the debugger settle it"&gt;&#10;&lt;figcaption&gt;Strings, rename, debugger, then back around for another pass.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;h2 id="start-with-strings-because-binaries-are-bad-at-keeping-secrets"&gt;Start with strings, because binaries are bad at keeping secrets&lt;/h2&gt;&#10;&lt;p&gt;The &lt;code&gt;strings&lt;/code&gt; command prints every readable piece of text inside a binary. Error messages, URLs, passwords someone forgot to hide. Half of beginner challenges fall over right here because the answer was sitting in plain text. Thirty seconds of work. Do this before anything clever.&lt;/p&gt;</description></item><item><title>How to Spy on Any Program (Legally)</title><link>https://hexrogue.github.io/blog/spy-on-any-program/</link><pubDate>Mon, 05 Dec 2022 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/spy-on-any-program/</guid><description>&lt;p&gt;Every program lies about what it does. Not maliciously. It just never tells you the full story. The installer says &amp;ldquo;quick setup&amp;rdquo; while writing files in six directories. The app says &amp;ldquo;no account needed&amp;rdquo; while phoning three analytics servers. It is not a conspiracy. It is a filing cabinet with no labels and a lock you can pick with strace.&lt;/p&gt;&#10;&lt;p&gt;After years of CTFs, homelab mysteries, and malware curiosity, I built a method for interrogating any program until it confesses. Five layers, cheapest first. This is the post I wish existed when I started.&lt;/p&gt;</description></item><item><title>OOP Clicked When I Stopped Memorizing</title><link>https://hexrogue.github.io/blog/oop-clicked-kitchen-version/</link><pubDate>Tue, 11 Oct 2022 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/oop-clicked-kitchen-version/</guid><description>&lt;p&gt;Object oriented programming confused me exactly as long as I tried to memorize definitions. Encapsulation, inheritance, polymorphism. Words to chant before exams, and also the name of a band that would never get a record deal. Then someone explained it with a kitchen, and it clicked in a minute. Passing that on.&lt;/p&gt;&#10;&lt;h2 id="classes-are-cookie-cutters-objects-are-cookies"&gt;Classes are cookie cutters, objects are cookies&lt;/h2&gt;&#10;&lt;p&gt;A class is a blueprint. It describes what a thing has (data) and what it can do (methods), but it is not the thing. An object is one actual thing stamped from the blueprint. One User class, thousands of user objects. The cutter is not a cookie. Say it with me.&lt;/p&gt;</description></item><item><title>I Learned to Code on a Phone</title><link>https://hexrogue.github.io/blog/coding-on-a-phone-termux-2020/</link><pubDate>Sun, 18 Sep 2022 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/coding-on-a-phone-termux-2020/</guid><description>&lt;p&gt;In 2020 I had no laptop. What I had was an Android phone, a charger that only worked at one angle, and a lot of free time. It was not a setup. It was a dare with a battery percentage. Everyone said you need a real computer to learn programming. My phone had other plans. This is the story of nano, Termux, and the year I coded with my thumbs.&lt;/p&gt;</description></item><item><title>Reviving a Dead Phone</title><link>https://hexrogue.github.io/blog/reviving-dead-phone/</link><pubDate>Sat, 30 Jul 2022 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/reviving-dead-phone/</guid><description>&lt;p&gt;My old phone stopped getting updates two years ago. Still good hardware, perfect for a home dashboard or a test device, except the stock ROM got slower with every year and the battery stats blamed everything except itself. It was the digital equivalent of a couch with a broken spring: technically furniture, functionally a threat. So I unlocked the bootloader and gave it a second life.&lt;/p&gt;&#10;&lt;h2 id="unlocking-is-the-easy-scary-part"&gt;Unlocking is the easy scary part&lt;/h2&gt;&#10;&lt;p&gt;Every vendor hides the unlock in a different menu and warns you like you are defusing something. Back up first, obviously, because unlocking wipes the device. Enable OEM unlocking, boot into fastboot, run the unlock command, confirm on the tiny volume-key menu while questioning your choices. The phone wipes itself and reboots like nothing happened, except now it trusts whatever you flash.&lt;/p&gt;</description></item><item><title>What I Learned From the Big Short</title><link>https://hexrogue.github.io/blog/what-i-learned-from-the-big-short/</link><pubDate>Mon, 23 May 2022 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/what-i-learned-from-the-big-short/</guid><description>&lt;p&gt;A movie about the 2008 crash made me pause every twenty minutes to google things. It is the only film where the villain is a spreadsheet and the jump scare is a credit default swap. The crash, explained like you are five, plus the part the movie gets wrong:&lt;/p&gt;&#10;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/city-towers.jpg" alt="Wall Street at 8 AM, probably"&gt;&#10;&lt;figcaption&gt;Wall Street at 8 AM, probably. Everyone inside is selling boxes.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;h2 id="the-crash-in-one-paragraph"&gt;The crash in one paragraph&lt;/h2&gt;&#10;&lt;p&gt;Banks gave home loans to people who could not pay. Then they packed thousands of those loans into boxes, sliced the boxes into pieces, and sold the pieces as safe investments. When homeowners stopped paying, every box turned out to be full of bad loans at once, and the banks holding the pieces nearly died in the same week. That is the whole 2008 crisis. Everything below is details.&lt;/p&gt;</description></item><item><title>Seven Ways I Broke My Own Website</title><link>https://hexrogue.github.io/blog/webdev-tips-what-to-avoid/</link><pubDate>Thu, 17 Feb 2022 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/webdev-tips-what-to-avoid/</guid><description>&lt;p&gt;I have shipped code that worked perfectly on my laptop and fell apart the moment a real user touched it. The laptop is a controlled environment. A real user is a raccoon with a credit card. These are the mistakes that cost me the most evenings. Read them now, or pay the same tuition later.&lt;/p&gt;&#10;&lt;h2 id="the-form-that-worked-until-someone-opened-curl"&gt;The form that worked until someone opened curl&lt;/h2&gt;&#10;&lt;p&gt;The browser is the attacker&amp;rsquo;s computer. Every check in your JavaScript is a suggestion. The attacker can skip it. Validate on the server, every time, even when the frontend already did. Frontend validation is for people who make typos. Backend validation is for everyone else.&lt;/p&gt;</description></item><item><title>Radare2: The Terminal Gremlin That Reads Binaries</title><link>https://hexrogue.github.io/blog/radare2-ultimate-guide/</link><pubDate>Tue, 16 Nov 2021 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/radare2-ultimate-guide/</guid><description>&lt;p&gt;Everyone told me to learn Ghidra. I learned the terminal gremlin instead. Ghidra is a cruise ship: big, comfortable, everything labeled. Radare2 is a jetski you assemble mid-ocean while it insults you. The jetski comes with a manual written in flags and a strong opinion about your free time. I use both now, but r2 is the one I reach for first, and this is the guide I wish existed when I started.&lt;/p&gt;</description></item><item><title>Dune Is About Single Points of Failure</title><link>https://hexrogue.github.io/blog/dune-spice-single-point/</link><pubDate>Tue, 02 Nov 2021 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/dune-spice-single-point/</guid><description>&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/wheat-field.jpg" alt="A desert that is definitely Arrakis"&gt;&#10;&lt;figcaption&gt;Arrakis, probably. (Not Arrakis.)&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;Dune looks like a story about a chosen one. I think it is a story about infrastructure. Specifically: what happens when your entire civilization has exactly one load bearing component, and it only grows on one planet, guarded by giant worms. That is not worldbuilding. That is a risk assessment screaming for help. It is also every startup with one database and a confident intern.&lt;/p&gt;</description></item><item><title>How Your CPU Reads Code</title><link>https://hexrogue.github.io/blog/cpu-how-it-reads-code/</link><pubDate>Tue, 21 Sep 2021 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/cpu-how-it-reads-code/</guid><description>&lt;p&gt;Computer organization sounded dry until week two, when I realized it answers the best question in computing: how do words I type become electricity doing math. My notebook version, short enough to read without a degree and long enough to sound smart at a dinner party you were not invited to:&lt;/p&gt;&#10;&lt;h2 id="everything-is-switches"&gt;Everything is switches&lt;/h2&gt;&#10;&lt;p&gt;A CPU understands exactly two things: on and off. Every photo, song, and game is patterns of ons and offs, ones and zeros. Eight of them make a byte, enough for one character. Billions of them make everything else. It feels absurd until you realize all of human language is also just patterns of a few dozen sounds. Same trick, different medium.&lt;/p&gt;</description></item><item><title>What an Operating System Actually Does</title><link>https://hexrogue.github.io/blog/os-what-it-actually-does/</link><pubDate>Tue, 03 Aug 2021 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/os-what-it-actually-does/</guid><description>&lt;p&gt;I am taking operating systems this semester, and the textbook reads like it was written by the scheduler itself: efficient, joyless, technically correct. So these are my notes, translated into human. Same facts, fewer footnotes, one joke per page.&lt;/p&gt;&#10;&lt;h2 id="your-os-is-a-middle-manager"&gt;Your OS is a middle manager&lt;/h2&gt;&#10;&lt;p&gt;Every program on your computer believes it owns the machine. Chrome thinks the CPU is its CPU. Your game thinks the memory is its memory. Both are wrong. The operating system sits between lying programs and finite hardware, handing out slices of CPU time so fast that everyone believes the lie. That illusion is the entire job.&lt;/p&gt;</description></item><item><title>Electrical Engineering Fundamentals, Without the Headache</title><link>https://hexrogue.github.io/blog/electrical-engineering-fundamentals/</link><pubDate>Wed, 09 Jun 2021 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/electrical-engineering-fundamentals/</guid><description>&lt;p&gt;I am a software guy. My world is if-else and semicolons. Then I touched electrical engineering and realized all my code runs on literal lightning we bullied into doing math. I have never trusted a semicolon since. So I learned the basics. Here is my notebook, translated into human.&lt;/p&gt;&#10;&lt;h2 id="voltage-is-pressure-current-is-flow"&gt;Voltage is pressure, current is flow&lt;/h2&gt;&#10;&lt;p&gt;Forget definitions for a sec. Picture a water pipe.&lt;/p&gt;&#10;&lt;p&gt;Voltage is how hard the water wants to move. Current is how much actually moves. Resistance is the narrow bit that says no. That mapping is the whole subject. Every confusing circuit I have hit turned into &amp;ldquo;wait, which part of the pipe is this.&amp;rdquo;&lt;/p&gt;</description></item><item><title>The Sun Does Not Need an API</title><link>https://hexrogue.github.io/blog/my-go-prayer-time-calculator/</link><pubDate>Mon, 12 Apr 2021 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/my-go-prayer-time-calculator/</guid><description>&lt;p&gt;I have stood in a basement carpark, holding my phone at the angle where hope lives, waiting for a prayer app to admit it needed the internet. No signal, no answer. For a prayer timetable. The Sun was directly above the building, no signal required. It has been running this service for about four billion years and has never once asked me to accept cookies.&lt;/p&gt;&#10;&lt;p&gt;That was the moment I decided to compute the times myself.&lt;/p&gt;</description></item><item><title>Tenet is easy once you stop thinking forwards</title><link>https://hexrogue.github.io/blog/tenet-backwards-theory/</link><pubDate>Mon, 14 Dec 2020 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/tenet-backwards-theory/</guid><description>&lt;p&gt;People call Tenet confusing. I think it is the simplest Nolan film, and that is exactly why it confuses everyone. My hypothesis: you are not supposed to follow the plot forwards. You are supposed to follow it the way you follow a receipt after a blackout: backwards, squinting, and hoping the total makes sense. You are supposed to follow the entropy.&lt;/p&gt;&#10;&lt;h2 id="the-one-rule-that-explains-everything"&gt;The one rule that explains everything&lt;/h2&gt;&#10;&lt;p&gt;Forget timelines. The film has exactly one rule: some things move backwards through time. A bullet that flies back into a gun. A car chase where one car un-crashes. Every &amp;ldquo;wait, what&amp;rdquo; moment is just this rule, applied consistently.&lt;/p&gt;</description></item><item><title>Brand Was Right: An Interstellar Theory</title><link>https://hexrogue.github.io/blog/interstellar-brand-was-right/</link><pubDate>Sat, 07 Nov 2020 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/interstellar-brand-was-right/</guid><description>&lt;p&gt;Everyone quotes Interstellar for the physics. Nobody defends the scene where Dr. Brand says love might be an artifact of a higher dimension. Audiences laughed. Physicists rolled their eyes. I did not laugh. I was too busy wondering why the robots had more emotional intelligence than the humans. I have rewatched this film four times and I am now convinced that speech is the entire movie in disguise. My hypothesis, in three parts:&lt;/p&gt;</description></item></channel></rss>