<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tips on Muhammad Nuh</title><link>https://hexrogue.github.io/tags/tips/</link><description>Recent content in Tips 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>Mon, 28 Apr 2025 00:00:00 +0800</lastBuildDate><atom:link href="https://hexrogue.github.io/tags/tips/index.xml" rel="self" type="application/rss+xml"/><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>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>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>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></channel></rss>