<?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 Bhaskar  Vikas on Medium]]></title>
        <description><![CDATA[Stories by Bhaskar  Vikas on Medium]]></description>
        <link>https://medium.com/@bhaskar.685.vikas?source=rss-cbefb173b6ec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_NB8QSk4EDWru9AA</url>
            <title>Stories by Bhaskar  Vikas on Medium</title>
            <link>https://medium.com/@bhaskar.685.vikas?source=rss-cbefb173b6ec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:08:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bhaskar.685.vikas/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[Linux 101 for Cybersecurity: Files, Permissions, Processes & Logs]]></title>
            <link>https://medium.com/@bhaskar.685.vikas/linux-101-for-cybersecurity-files-permissions-processes-logs-60d48d00709d?source=rss-cbefb173b6ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/60d48d00709d</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[linux-tutorial]]></category>
            <dc:creator><![CDATA[Bhaskar  Vikas]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 02:11:25 GMT</pubDate>
            <atom:updated>2026-10-08T02:11:25.440Z</atom:updated>
            <content:encoded><![CDATA[<p>When I started learning cybersecurity, everyone kept telling me the same thing: learn Linux first. I didn’t get why. I thought I could just learn the security tools and figure out the rest later.</p><p>I was wrong. Almost every server, cloud machine, and security tool runs on Linux. If you want to investigate an attack, harden a system, or even just practice on platforms like TryHackMe, you will be sitting in a Linux terminal. So let’s go through the four basics that matter most: files, permissions, processes, and logs.</p><p>You don’t need to memorize everything. Just understand why each one matters for security.</p><h3>1. Files and Directories</h3><p>In Linux, everything is a file. Your documents, your settings, your devices, even running programs show up as files somewhere. That is why knowing your way around the file system is the first skill to build.</p><p>Here are the commands you will use all the time:</p><ul><li>pwd shows where you are right now</li><li>ls -la lists everything in a folder, including hidden files</li><li>cd /var/log moves you into a folder</li><li>cat file.txt prints what is inside a file</li><li>find / -name &quot;*.conf&quot; searches for files by name</li></ul><p>A few folders are worth knowing about:</p><ul><li>/etc holds configuration files, including user account info</li><li>/var/log holds the log files (we&#39;ll come back to this)</li><li>/home is where regular users keep their stuff</li><li>/tmp is a temporary folder that anyone can write to</li><li>/root is the home folder of the root user, the admin</li></ul><p><strong>Why this matters for security:</strong> Attackers love /tmp because almost anyone can write there, so malware often gets dropped in it. They also look at /etc/passwd and /etc/shadow to find user accounts and password hashes. And hidden files (anything starting with a dot) can hide things like backdoors or saved credentials. Always use ls -la and not just ls.</p><h3>2. Permissions</h3><p>This is the part that confused me the most at first, but it is simple once you see it. Run this:</p><p>ls -l</p><p>You will see something like:</p><p>-rwxr-xr-- 1 alice staff 1200 Oct 8 notes.sh</p><p>That first part, -rwxr-xr--, is the permission string. Break it into pieces:</p><ul><li>The first character tells you the type. A dash means a normal file, and d means a directory.</li><li>The next three (rwx) are the owner&#39;s permissions.</li><li>The next three (r-x) are the group&#39;s permissions.</li><li>The last three (r--) are for everyone else.</li></ul><p>The letters mean:</p><ul><li>r is read</li><li>w is write</li><li>x is execute (run it as a program)</li></ul><p>Permissions can also be written as numbers. Read is 4, write is 2, execute is 1. You add them up. So rwx is 7, r-x is 5, and r-- is 4. That is why you will see chmod 755 file and chmod 644 file everywhere.</p><p>To change permissions, use chmod. To change the owner, use chown.</p><p><strong>Why this matters for security:</strong> Bad permissions are one of the most common weaknesses on a system. If a file with passwords is readable by everyone, that is a problem. If a script that runs as root can be edited by a normal user, that user can take over the machine. A setting like chmod 777 gives everybody full access, and you should almost never see it on a real system.</p><p>Also look out for something called SUID. It is a special permission that makes a program run as its owner (often root) no matter who starts it. You can find these files with:</p><p>find / -perm -4000 2&gt;/dev/null</p><p>Some SUID files are normal, like passwd. But an odd one in a strange place is a classic way attackers move up to root. This command is one of the first things people run in capture the flag challenges.</p><h3>3. Processes</h3><p>A process is just a program that is running. Your browser is a process. A web server is a process. And yes, malware is also a process when it is running.</p><p>The commands to start with:</p><ul><li>ps aux shows all running processes</li><li>top shows live usage, like a task manager</li><li>ps aux | grep ssh filters the list to just what you are looking for</li><li>kill 1234 stops the process with ID 1234</li><li>kill -9 1234 forces it to stop if it won&#39;t listen</li></ul><p>When you run ps aux, pay attention to these columns: the <strong>user</strong> running it, the <strong>PID</strong> (process ID), the <strong>CPU and memory</strong> use, and the <strong>command</strong> at the end.</p><p><strong>Why this matters for security:</strong> When you think a machine is compromised, looking at running processes is one of the first things you do. Ask yourself a few simple questions:</p><ul><li>Is anything running that I don’t recognize?</li><li>Is a process using a lot of CPU for no reason? (Crypto miners do this.)</li><li>Is a normal-looking program running from a weird place like /tmp?</li><li>Is something running as root that shouldn’t be?</li></ul><p>If you want to see what network connections a process is making, try ss -tulpn or netstat -tulpn. A process listening on a port you didn&#39;t set up is a big warning sign.</p><h3>4. Logs</h3><p>Logs are the diary of your system. They record who logged in, what failed, what got installed, and what went wrong. If something bad happens, the logs are where you find out how.</p><p>Most of them live in /var/log. The ones you should know:</p><ul><li>/var/log/auth.log (Debian and Ubuntu) or /var/log/secure (Red Hat and CentOS) records logins and sudo usage</li><li>/var/log/syslog or /var/log/messages records general system activity</li><li>/var/log/apache2/ or /var/log/nginx/ records web server traffic</li><li>/var/log/kern.log records kernel messages</li></ul><p>How to read them:</p><ul><li>tail -f /var/log/auth.log shows new lines live as they come in</li><li>grep &quot;Failed password&quot; /var/log/auth.log finds failed login attempts</li><li>less /var/log/syslog lets you scroll through a big file</li><li>last shows recent logins</li><li>journalctl -u ssh reads logs on systems that use systemd</li></ul><p><strong>Why this matters for security:</strong> Say you see 500 lines of “Failed password” for the same account in two minutes from one IP address. That is a brute force attack. Say you then see a “Accepted password” line from that same IP. Now you know they got in, and you know the time, so you can look at what happened next.</p><p>Here is a useful trick to count failed logins by IP:</p><p>grep &quot;Failed password&quot; /var/log/auth.log | awk &#39;{print $(NF-3)}&#39; | sort | uniq -c | sort -nr</p><p>It looks scary, but it just pulls out the IP addresses, counts them, and sorts the biggest number to the top. Good for a quick look at who is hammering your server.</p><p>One more thing. Attackers know logs expose them, so they often try to delete or edit them. If you see logs with big gaps or a log file that is suddenly empty, treat that as suspicious in itself.</p><h3>Putting It All Together</h3><p>Imagine you get an alert that a server is acting strange. Here is how you might use all four skills:</p><ol><li>Check the <strong>logs</strong> to see if anyone logged in at a strange time.</li><li>Check the <strong>processes</strong> to see if something unknown is running.</li><li>Check the <strong>files</strong>, especially /tmp and hidden files, for anything new.</li><li>Check the <strong>permissions</strong> to see if something has been changed to give someone too much access.</li></ol><p>That is a real, basic investigation workflow. Nothing fancy, and it works.</p><h3>How to Practice</h3><p>Reading is not enough. You need to type the commands yourself. A few free ways to do that:</p><ul><li>Install Ubuntu or Kali in a virtual machine using VirtualBox</li><li>Try the Linux rooms on TryHackMe</li><li>Play OverTheWire’s Bandit game, which teaches Linux step by step</li><li>Break things on purpose in your VM, then fix them</li></ul><p>Don’t practice on a machine you care about, and don’t run these commands on systems you don’t have permission to touch.</p><h3>Final Thoughts</h3><p>Linux can feel like a lot at the start, and that is normal. I still look up commands all the time. But once you get comfortable with files, permissions, processes, and logs, a lot of cybersecurity starts to make sense. You stop just copying commands and start understanding what is happening on the system.</p><p>Start small. Open a terminal today, run ls -la, look around, and keep going from there.</p><p>If this helped you, leave a clap or a comment and tell me what you want to learn next. Maybe networking commands or Bash scripting for security?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60d48d00709d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 Linux Problems Every Beginner Has Experienced]]></title>
            <link>https://medium.com/@bhaskar.685.vikas/8-linux-problems-every-beginner-has-experienced-6ee54ab7b90a?source=rss-cbefb173b6ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ee54ab7b90a</guid>
            <category><![CDATA[basics-linux]]></category>
            <category><![CDATA[linux-mint]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[command-line]]></category>
            <category><![CDATA[linux-tutorial]]></category>
            <dc:creator><![CDATA[Bhaskar  Vikas]]></dc:creator>
            <pubDate>Thu, 17 Sep 2026 03:04:57 GMT</pubDate>
            <atom:updated>2026-09-17T03:04:57.759Z</atom:updated>
            <content:encoded><![CDATA[<p>So you finally took the plunge and installed Linux. Maybe you dual-booted Ubuntu next to Windows, spun up a Raspberry Pi, or got curious after hearing your developer friends rave about it. Whatever brought you here, welcome to the club — and also, welcome to the growing pains.</p><p>Every Linux user, no matter how skilled they are now, started exactly where you are: confused, a little frustrated, and Googling error messages at 1 a.m. Here are eight problems nearly every beginner runs into, why they happen, and how to get past them.</p><h3>1. “Permission Denied” Everywhere</h3><p>You try to run a script, edit a file, or install something, and Linux slams the door in your face with Permission denied. Coming from Windows or macOS, where you&#39;re usually the all-powerful admin by default, this can feel baffling.</p><p><strong>Why it happens:</strong> Linux takes its multi-user, security-first design seriously. Files and folders have owners, groups, and permission levels, and by default you can’t just do whatever you want to system files.</p><p><strong>The fix:</strong> Learn the basics of chmod, chown, and sudo. Understand <em>why</em> a command needs elevated privileges before blindly typing sudo in front of everything — that habit gets dangerous fast.</p><h3>2. Package Manager Confusion</h3><p>You want to install an app. On Windows, you’d download an .exe. On Linux, you&#39;re suddenly faced with apt, dnf, pacman, snap, flatpak, or a random .deb file you found on a forum — and none of them behave quite the same.</p><p><strong>Why it happens:</strong> Unlike Windows or macOS, Linux doesn’t have one single “app store” model. Different distributions use different package managers, and newer universal formats (Snap, Flatpak, AppImage) were layered on top over the years.</p><p><strong>The fix:</strong> Learn the package manager for <em>your</em> specific distro first (e.g., apt for Ubuntu/Debian, dnf for Fedora). Once that clicks, the others start making sense by comparison.</p><h3>3. The Terminal Feels Like a Foreign Language</h3><p>You open a guide, and it says “just run this command,” followed by a wall of text with dashes, pipes, and symbols you’ve never seen. It’s intimidating, and one typo can feel like it broke everything.</p><p><strong>Why it happens:</strong> The terminal is powerful precisely because it’s dense and literal — every character matters. There’s no friendly GUI softening the blow.</p><p><strong>The fix:</strong> Don’t try to memorize commands. Learn to <em>read</em> them — understand what flags (-r, -f, -v) generally mean, and get comfortable typing command --help or man command before running anything unfamiliar.</p><h3>4. Broken Drivers (Especially Wi-Fi and Graphics)</h3><p>You install Linux, reboot, and suddenly your Wi-Fi card isn’t detected, or your graphics card is running in some low-resolution potato mode.</p><p><strong>Why it happens:</strong> Hardware manufacturers often prioritize Windows drivers, and some components (particularly certain Wi-Fi chipsets and Nvidia GPUs) need proprietary drivers that aren’t installed out of the box due to licensing restrictions.</p><p><strong>The fix:</strong> Before installing, quickly search “[your laptop model] + Linux compatibility.” Many distros now have built-in tools (like Ubuntu’s “Additional Drivers”) to install proprietary drivers with a few clicks.</p><h3>5. Dependency Hell</h3><p>You try to install one program, and it demands five other packages, which demand three more, and one of them conflicts with something already on your system. Suddenly your simple install has spiraled into an afternoon-long troubleshooting session.</p><p><strong>Why it happens:</strong> Linux software often relies on shared libraries rather than bundling everything into one package. When versions mismatch across programs, conflicts happen.</p><p><strong>The fix:</strong> Stick to your distro’s official repositories when possible, and lean on containerized formats like Flatpak or Snap for tricky apps — they bundle their own dependencies and avoid a lot of this mess.</p><h3>6. Updates That Break Things</h3><p>You run a routine system update, reboot, and now your desktop won’t load, or an app you use daily has vanished or stopped working.</p><p><strong>Why it happens:</strong> Linux moves fast, especially on rolling-release or bleeding-edge distros. Updates can introduce incompatibilities, especially with graphics drivers or kernel changes.</p><p><strong>The fix:</strong> If stability matters more to you than having the newest features, choose a Long-Term Support (LTS) release. Also, learn how to boot into a previous kernel version from the boot menu — it’s a lifesaver.</p><h3>7. Choosing a Distro Feels Impossible</h3><p>Before you even install anything, you’re hit with a paralyzing question: Ubuntu? Fedora? Mint? Arch? Pop!_OS? Debian? Every forum thread has fifty opinions and everyone sounds absolutely certain theirs is correct.</p><p><strong>Why it happens:</strong> Linux’s open-source nature means there are hundreds of distributions, each with different philosophies, package managers, and target audiences. There’s no single “official” version.</p><p><strong>The fix:</strong> For beginners, this decision matters far less than forums make it seem. Ubuntu, Linux Mint, or Fedora are all solid, well-documented starting points. Pick one, use it for a few months, and you’ll naturally develop opinions about what you actually want.</p><h3>8. Fear of “Breaking” the System</h3><p>Maybe the most universal beginner experience: a low-grade anxiety every time you open the terminal, convinced that one wrong command will destroy your entire installation.</p><p><strong>Why it happens:</strong> Linux gives you real power over your system, and early on you don’t yet have the intuition for what’s safe and what’s genuinely risky (looking at you, rm -rf).</p><p><strong>The fix:</strong> Use a virtual machine or a spare device to experiment fearlessly. Learn what your backups look like <em>before</em> you need them. And remember — reinstalling Linux is not a big deal. Most experienced users have done it dozens of times, often on purpose.</p><h3>The Bottom Line</h3><p>Every one of these frustrations is a rite of passage, not a sign you’re doing something wrong. Linux rewards curiosity and patience — the very struggles that make it confusing at first are usually what make it so powerful and customizable once things click. Stick with it, keep a search engine handy, and in a few months you’ll be the one explaining chmod to the next beginner.</p><p>Just getting started with Linux? Subscribe to get our beginner-friendly guides delivered straight to your inbox — no jargon, no gatekeeping, just practical help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ee54ab7b90a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Burp Suite — Complete Study Guide]]></title>
            <link>https://medium.com/@bhaskar.685.vikas/burp-suite-complete-study-guide-521621f8eb61?source=rss-cbefb173b6ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/521621f8eb61</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[burpsuite]]></category>
            <dc:creator><![CDATA[Bhaskar  Vikas]]></dc:creator>
            <pubDate>Sat, 12 Sep 2026 02:18:54 GMT</pubDate>
            <atom:updated>2026-09-12T02:18:54.946Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>A structured reference for learning Burp Suite: architecture, every core tool, key features, and the Linux commands that pair with it during web application penetration testing.</em></blockquote><h3>1. What is Burp Suite?</h3><p>Burp Suite is an integrated platform (by PortSwigger) for <strong>web application security testing</strong>. It works as an <strong>intercepting proxy</strong> — it sits between your browser and the target server, letting you view, intercept, and modify every HTTP/HTTPS request and response.</p><p><strong>Editions:</strong></p><p>Edition Use Case Community Free, manual testing only, no scanner, rate-limited Intruder Professional Paid, full scanner, unlimited Intruder speed, extensions Enterprise CI/CD integration, scheduled scans, dashboards</p><h3>2. Installation on Linux</h3><pre># Option 1: Kali Linux (pre-installed)<br>burpsuite</pre><pre># Option 2: Manual install (download .sh from portswigger.net)<br>chmod +x burpsuite_community_linux.sh<br>./burpsuite_community_linux.sh</pre><pre># Option 3: Via snap<br>sudo snap install burpsuite</pre><pre># Check Java (Burp needs Java 17+)<br>java -version</pre><pre># Launch from terminal<br>burpsuite &amp;</pre><h3>3. Core Architecture</h3><pre>Browser  &lt;---&gt;  Burp Proxy (127.0.0.1:8080)  &lt;---&gt;  Target Server</pre><p>Burp acts as a <strong>Man-in-the-Middle (MITM)</strong> proxy between your browser and the web app, so you can inspect/edit traffic in real time.</p><h3>4. Setting Up the Proxy (Linux + Browser)</h3><h3>4.1 Configure Browser Proxy</h3><ul><li>Firefox → Settings → Network Settings → Manual proxy: 127.0.0.1 port 8080</li><li>Or use <strong>FoxyProxy</strong> extension for quick toggling</li></ul><h3>4.2 Install Burp’s CA Certificate (for HTTPS interception)</h3><pre># 1. With proxy on, visit in browser:<br>http://burp   # or http://burpsuite</pre><pre># 2. Download cacert.der, then convert &amp; trust it (Linux/Firefox uses NSS store,<br>#    but for system-wide trust on Debian/Ubuntu):<br>openssl x509 -inform DER -in cacert.der -out burp_cert.pem</pre><pre>sudo cp burp_cert.pem /usr/local/share/ca-certificates/burp_cert.crt<br>sudo update-ca-certificates</pre><h3>4.3 Using curl/other tools through Burp</h3><pre>curl -x http://127.0.0.1:8080 -k https://target.com<br>curl --proxy 127.0.0.1:8080 --insecure https://target.com</pre><h3>5. Burp Suite Tools (Tab by Tab)</h3><h3>5.1 Proxy</h3><p>The heart of Burp. Intercepts browser traffic before it reaches the server.</p><ul><li><strong>Intercept tab</strong> — pause and edit requests live</li><li><strong>HTTP History</strong> — log of every request/response</li><li><strong>WebSockets History</strong> — logs WS traffic</li><li><strong>Match and Replace</strong> — auto-modify traffic (e.g., replace User-Agent)</li><li><strong>Response interception</strong> — edit server responses before they reach browser</li></ul><p><strong>Key actions:</strong> Forward, Drop, Intercept On/Off, Send to Repeater/Intruder/Comparer</p><h3>5.2 Target</h3><ul><li><strong>Site map</strong> — tree view of all discovered URLs/endpoints</li><li><strong>Scope</strong> — define what’s in/out of testing boundary (critical — keeps scans/attacks limited to authorized targets)</li><li>Right-click any host → “Add to scope”</li></ul><pre># Example: only target a lab domain to stay in scope<br># Set scope: Target &gt; Scope &gt; Add &gt; *.testlab.local</pre><h3>5.3 Repeater</h3><p>Manually resend and tweak individual HTTP requests repeatedly. Used for:</p><ul><li>Testing parameter tampering</li><li>Manual SQLi/XSS payload testing</li><li>Observing how small changes affect server response</li></ul><p>Shortcut: Ctrl+R sends selected request to Repeater.</p><h3>5.4 Intruder</h3><p>Automated attack tool for fuzzing/brute-forcing.</p><p><strong>Attack types:</strong></p><p>Type Description Sniper One payload set, one position at a time Battering ram Same payload in all positions simultaneously Pitchfork Multiple payload sets, moved in parallel Cluster bomb Multiple payload sets, all combinations tested</p><p>Used for: brute-forcing logins, fuzzing parameters, enumerating IDs.</p><p><em>(Community edition throttles Intruder speed — Pro removes this limit.)</em></p><h3>5.5 Scanner (Pro only)</h3><p>Automated vulnerability scanner:</p><ul><li><strong>Crawl</strong> — maps the app</li><li><strong>Audit</strong> — actively tests for vulnerabilities (SQLi, XSS, SSRF, XXE, etc.)</li><li>Generates a full report with severity ratings</li></ul><h3>5.6 Decoder</h3><p>Encode/decode data: Base64, URL, HTML, Hex, ASCII, Gzip.</p><p>Linux equivalents for cross-checking:</p><pre>echo -n &quot;admin:password&quot; | base64<br>echo &quot;YWRtaW46cGFzc3dvcmQ=&quot; | base64 -d<br>python3 -c &quot;import urllib.parse; print(urllib.parse.quote(&#39;a b&amp;c&#39;))&quot;</pre><h3>5.7 Comparer</h3><p>Diff two requests/responses side by side (word or byte level) — useful to spot subtle differences in behavior between valid/invalid inputs.</p><h3>5.8 Sequencer</h3><p>Analyzes randomness/entropy of tokens (session IDs, CSRF tokens) to check if they’re predictable.</p><h3>5.9 Extender / BApp Store</h3><p>Add plugins/extensions (written in Java, Python via Jython, or Ruby via JRuby). Popular extensions: Autorize, Turbo Intruder, Logger++, J2EEScan, Active Scan++.</p><h3>5.10 Logger</h3><p>Central log of all traffic across all tools (newer Burp versions merged this in).</p><h3>6. Key Features Summary</h3><p>Feature Purpose Intercepting Proxy View/modify live HTTP(S) traffic Spidering/Crawling Auto-discover site structure Active/Passive Scanning Find vulnerabilities automatically (Pro) Intruder Automated fuzzing &amp; brute force Repeater Manual request replay/testing Sequencer Token randomness analysis Decoder Encoding/decoding utility Comparer Diff requests/responses Extensibility Custom plugins via BApp Store Collaborator (Pro) Detect out-of-band (OOB) vulnerabilities like blind SSRF/XXE</p><h3>7. Typical Testing Workflow</h3><pre># 1. Start Burp<br>burpsuite &amp;</pre><pre># 2. Set browser proxy to 127.0.0.1:8080, install CA cert</pre><pre># 3. Browse the target app manually (Proxy captures traffic)</pre><pre># 4. Define scope in Target tab</pre><pre># 5. Send interesting requests to Repeater for manual testing<br>#    (right click -&gt; Send to Repeater)</pre><pre># 6. Fuzz parameters via Intruder</pre><pre># 7. Run Scanner (Pro) for automated vuln discovery</pre><pre># 8. Use Decoder/Comparer as needed during analysis</pre><pre># 9. Export findings/report</pre><h3>8. Useful Linux Commands Alongside Burp</h3><h3>Network &amp; reconnaissance</h3><pre># Check what&#39;s listening on Burp&#39;s proxy port<br>sudo netstat -tulnp | grep 8080<br>ss -tulnp | grep 8080</pre><pre># DNS/subdomain enumeration before importing targets into Burp<br>nslookup target.com<br>dig target.com<br>whois target.com</pre><pre># Port scan target before testing<br>nmap -sV -Pn target.com</pre><h3>Working with Burp’s exported files</h3><pre># Burp can export requests as raw HTTP files - replay with curl<br>curl -X POST --data-binary @request.txt http://target.com --insecure</pre><pre># Extract Burp project data (for automation/scripts)<br>grep -i &quot;Cookie:&quot; request.txt</pre><h3>Automating with command line + Burp REST API (Pro/Enterprise)</h3><pre># Trigger a scan via Burp&#39;s REST API<br>curl -X POST http://127.0.0.1:1337/v0.1/scan \<br>  -H &quot;Content-Type: application/json&quot; \<br>  -d &#39;{&quot;urls&quot;: [&quot;https://target.com&quot;]}&#39;</pre><h3>SSL/Certificate troubleshooting</h3><pre>openssl s_client -connect target.com:443 -showcerts</pre><h3>Proxy chaining (Burp -&gt; Tor, or Burp -&gt; another proxy)</h3><pre># Route Burp&#39;s outbound traffic through another proxy using proxychains<br>proxychains burpsuite</pre><h3>9. Common Interview / Exam Topics Checklist</h3><ul><li>[ ] Difference between Proxy interception and passive spidering</li><li>[ ] Repeater vs Intruder use cases</li><li>[ ] 4 Intruder attack types and when to use each</li><li>[ ] How Burp handles HTTPS (CA cert, MITM)</li><li>[ ] Scope configuration and why it matters (legal/ethical boundary)</li><li>[ ] Sequencer’s role in session token security</li><li>[ ] Extender/BApp Store extensibility</li><li>[ ] Manual testing (Repeater) vs automated scanning (Scanner) trade-offs</li><li>[ ] Out-of-band testing via Collaborator</li></ul><h3>10. Notes on Legal Use</h3><p>Burp Suite should only be used on:</p><ul><li>Applications you own</li><li>Authorized penetration testing engagements (signed scope/contract)</li><li>Legal practice labs (PortSwigger Web Security Academy, DVWA, Juice Shop, HackTheBox, TryHackMe)</li></ul><p>Unauthorized testing of systems you don’t have permission for is illegal in most jurisdictions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=521621f8eb61" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Cybersecurity Mistakes Beginners Make That Are Actually Funny]]></title>
            <link>https://medium.com/@bhaskar.685.vikas/6-cybersecurity-mistakes-beginners-make-that-are-actually-funny-3303cced09b4?source=rss-cbefb173b6ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/3303cced09b4</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[internet-safety]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[beginners-guide]]></category>
            <category><![CDATA[humor]]></category>
            <dc:creator><![CDATA[Bhaskar  Vikas]]></dc:creator>
            <pubDate>Tue, 08 Sep 2026 04:11:00 GMT</pubDate>
            <atom:updated>2026-09-08T04:11:00.846Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QGD3dQzztJJZuPbYn8kk0w.jpeg" /></figure><p><em>Because nothing says “I understand security” like a Post-it note with your password on your monitor.</em></p><p>Cybersecurity is serious business. Data breaches cost companies millions. Identity theft ruins lives. Nation-states hack power grids. And yet, somehow, most of us are out here using “password123” and calling it a day.</p><p>If you’re new to the world of cybersecurity — whether you’re a beginner IT admin, a small business owner, or just someone who finally realized “qwerty” isn’t a great password — you’ve probably made at least one of these mistakes. Don’t worry. We’ve all been there. Let’s laugh about it together, then go fix it immediately.</p><h3>1. The Password That’s Just the Word “Password”</h3><p>Somewhere out there, a beginner is proudly protecting their entire digital life with the password “Password1!” because it has a capital letter, a number, <em>and</em> a symbol. Technically compliant. Spiritually hilarious.</p><p>Security experts call this “security theater.” Hackers call it “Tuesday.”</p><p><strong>The fix:</strong> Use a password manager. Let it generate a 20-character string of chaos that even you can’t remember. That’s the point.</p><h3>2. Writing the Password on a Sticky Note (On the Monitor)</h3><p>You changed your password. Great job! You also wrote it down on a sticky note and stuck it directly on your monitor, in full view of anyone who walks past your desk — including the office cleaner, your nosy coworker, and that one guy from accounting who definitely photographs things for fun.</p><p>Congratulations, you’ve just converted a digital security problem into a physical one, and physical security is somehow <em>easier</em> to breach.</p><p><strong>The fix:</strong> If you must write it down, put it somewhere that isn’t visible from space.</p><h3>3. Clicking “Enable Macros” Because the Document Told You To</h3><p>A stranger emails you a Word document titled URGENT_INVOICE_FINAL_v2.docx. You open it. A banner pops up: &quot;This document requires macros to be enabled to view content.&quot;</p><p>You enable them. Because the document <em>asked nicely</em>.</p><p>Congratulations, you’ve just given a total stranger’s code permission to run on your machine, and somewhere a hacker is buying themselves a nice dinner with your data.</p><p><strong>The fix:</strong> If a document is begging you to enable macros, that’s not a feature request — that’s a red flag wearing a tiny disguise.</p><h3>4. Reusing the Same Password Everywhere</h3><p>You’ve got one glorious password. It’s strong. It’s got everything — uppercase, lowercase, a number, your dog’s name backwards. And you use it for your email, your bank, your Spotify, your work laptop, and that one forum you joined in 2014 to talk about houseplants.</p><p>That forum gets breached. Now your bank password is public knowledge, because hackers love nothing more than trying your leaked password everywhere else. It’s called “credential stuffing,” and it works embarrassingly often.</p><p><strong>The fix:</strong> Unique passwords everywhere. Yes, even for the houseplant forum.</p><h3>5. Turning Off the Antivirus Because It’s “Annoying”</h3><p>Your antivirus software popped up a warning while you were trying to download a “free” version of expensive software from a website that looks like it was designed in 1998. Instead of taking the hint, you disabled the antivirus entirely — problem solved!</p><p>Except the problem wasn’t solved. The problem was invited in, offered a snack, and shown to the guest room.</p><p><strong>The fix:</strong> If your antivirus is screaming at you, that’s not it being dramatic. That’s it doing its one job.</p><h3>6. Falling for “Congratulations, You’ve Won!” Emails</h3><p>You’ve just won a free iPhone, a Nigerian inheritance, and a suspiciously generous gift card from a store you’ve never shopped at, all in the same week. You didn’t enter any contests. You don’t know any Nigerian princes. But hey, free stuff!</p><p>You click the link. You “verify your identity” by typing in your actual identity. Somewhere, a phishing kit developer adds another success to their spreadsheet.</p><p><strong>The fix:</strong> If you didn’t enter, you didn’t win. This applies to lotteries, raffles, and suspiciously generous strangers online.</p><h3>7. Connecting to “Free Public WiFi_Definitely_Not_A_Trap”</h3><p>You’re at the airport. You’re tired. You see a WiFi network called “Airport_Free_WiFi” and one called “Airport Free WiFi (FASTER)” and you pick the faster one because obviously that one’s legit.</p><p>You then proceed to log into your bank account, check your work email, and message your boss, all over a network that could very well be a laptop in someone’s backpack three gates down, quietly collecting everything you type.</p><p><strong>The fix:</strong> Use a VPN on public WiFi, or better yet, just use your phone’s hotspot and let public WiFi be somebody else’s problem.</p><h3>The Real Lesson Here</h3><p>Every one of these mistakes is funny because it’s relatable — we’ve all cut a corner we knew we shouldn’t have. But the gap between “funny mistake” and “expensive data breach” is often just a matter of luck.</p><p>The good news? Fixing most of these takes minutes: a password manager, two-factor authentication, a healthy suspicion of free iPhones, and the willpower to leave your antivirus alone. Cybersecurity doesn’t have to be intimidating — it just has to be taken slightly more seriously than “Password1!”</p><p>So go forth, laugh at your past mistakes, and maybe change that sticky note password today. Your future self (and your IT department) will thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3303cced09b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 Linux Commands Every Cybersecurity Nerd Secretly Loves]]></title>
            <link>https://medium.com/@bhaskar.685.vikas/8-linux-commands-every-cybersecurity-nerd-secretly-loves-79161afcf0ce?source=rss-cbefb173b6ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/79161afcf0ce</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[command-line]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Bhaskar  Vikas]]></dc:creator>
            <pubDate>Thu, 03 Sep 2026 15:24:18 GMT</pubDate>
            <atom:updated>2026-09-03T15:24:18.722Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9RIm314751CvE4qaEhlQAg.png" /></figure><p>Ask any security professional what tool changed the way they work, and you might expect a name like Metasploit, Wireshark, or Burp Suite. But behind almost every flashy tool is a terminal — and inside that terminal, a handful of humble commands doing the real work.</p><p>These aren’t exotic. Most of them ship with every Linux distro by default. But once you understand how security folks <em>actually</em> use them, you start seeing them everywhere: in incident response playbooks, in CTF writeups, in the muscle memory of anyone who’s spent a 2 a.m. shift chasing down a compromised box.</p><p>Here are 8 commands that quietly run the cybersecurity world.</p><h3>1. grep — The Needle-Finder</h3><p>On the surface, grep just searches text. In security work, it&#39;s how you find the one malicious line buried in a 40,000-line log file.</p><pre>grep -i &quot;failed password&quot; /var/log/auth.log</pre><p>Pair it with -r for recursive searches across directories, or -E for extended regex, and suddenly you&#39;re hunting for IOCs (indicators of compromise) across an entire filesystem in seconds.</p><p><strong>Why nerds love it:</strong> It’s fast, it’s everywhere, and it turns “search this haystack” from a chore into a one-liner.</p><h3>2. netstat / ss — Who&#39;s Talking to Whom</h3><p>Every connection your machine makes — inbound or outbound — has to show up somewhere. netstat (or its modern, faster replacement ss) shows you exactly that.</p><pre>ss -tulpn</pre><p>This lists listening ports, the processes behind them, and active connections. If malware phones home, this is often the first place you’ll catch it.</p><p><strong>Why nerds love it:</strong> It turns an invisible network into a readable table.</p><h3>3. tcpdump — Packets, Raw and Unfiltered</h3><p>When you need to see <em>exactly</em> what’s crossing the wire, tcpdump gives you packet-level truth, no GUI required.</p><pre>tcpdump -i eth0 port 443</pre><p>It’s the command-line ancestor of Wireshark, and for quick checks on a remote server (where you can’t exactly pop open a GUI), it’s often faster than the alternative.</p><p><strong>Why nerds love it:</strong> There’s a certain honesty to raw packet data — nothing’s been summarized or interpreted for you.</p><h3>4. chmod / chown — The Guardians of Permission</h3><p>Misconfigured permissions are one of the most common — and most preventable — security holes. chmod and chown are how you lock things down (or, during an audit, how you find what someone left wide open).</p><pre>find / -perm -4000 -type f 2&gt;/dev/null</pre><p>That one-liner hunts for SUID binaries — a classic privilege escalation target. Understanding permissions isn’t glamorous, but it’s foundational.</p><p><strong>Why nerds love it:</strong> Nearly every privilege escalation writeup eventually comes back to a permission that shouldn’t have been set.</p><h3>5. lsof — List Open Files, Reveal Open Secrets</h3><p>“Everything is a file” is a Unix philosophy — which means lsof (list open files) can show you almost anything a process is touching: files, sockets, pipes, devices.</p><pre>lsof -i :4444</pre><p>That command tells you exactly which process is bound to a suspicious port — incredibly useful when hunting reverse shells or unexpected listeners.</p><p><strong>Why nerds love it:</strong> It bridges the gap between “a port is open” and “here’s the exact process responsible.”</p><h3>6. strings — Making Binaries Confess</h3><p>Malware analysis often starts here. strings pulls readable text out of binary files — URLs, IP addresses, error messages, even developer comments left behind by accident.</p><pre>strings suspicious_file.exe | grep http</pre><p>It’s crude compared to full reverse engineering, but it’s often the fastest way to get a first impression of what a file is actually trying to do.</p><p><strong>Why nerds love it:</strong> It’s the “quick glance” that saves hours of deeper analysis.</p><h3>7. iptables (or nftables) — The Gatekeeper</h3><p>Firewalls sound complicated until you realize they boil down to a set of rules about what traffic gets in and out. iptables is the classic Linux way to define those rules directly.</p><pre>iptables -A INPUT -p tcp --dport 22 -s 192.168.1.100 -j ACCEPT</pre><p>That single line locks down SSH access to one trusted IP. Multiply that logic across a server, and you’ve built a real perimeter.</p><p><strong>Why nerds love it:</strong> There’s something satisfying about controlling network traffic with plain, readable rules instead of clicking through a dashboard.</p><h3>8. nmap — The Reconnaissance Classic</h3><p>No list like this is complete without nmap. It&#39;s the tool that answers the question every security assessment starts with: <em>what&#39;s actually out there?</em></p><pre>nmap -sV -O 192.168.1.0/24</pre><p>That scans a subnet, fingerprinting live hosts, open ports, and running services. It’s often the very first command run in a penetration test — and one of the most misused if pointed at systems you don’t have permission to scan.</p><p><strong>Why nerds love it:</strong> It turns an unknown network into a map. Just remember: only scan systems you’re authorized to test.</p><h3>The Common Thread</h3><p>None of these commands are secret. They’re not zero-days, they’re not underground tools traded on forums — they’re built into nearly every Linux system on Earth. What makes them beloved isn’t obscurity; it’s versatility. A defender uses grep to hunt for compromise. An attacker (ethically, in a test environment) uses it to sift through loot. Both use nmap to understand a network, just from opposite sides of the table.</p><p>That’s the real secret cybersecurity nerds know: mastery isn’t about having exotic tools. It’s about knowing a small set of powerful ones so well that you can bend them to whatever problem shows up at 2 a.m.</p><p><em>Got a favorite command that didn’t make the list? That’s what the comments are for.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79161afcf0ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Linux Error Messages That Read Like Passive-Aggressive Notes]]></title>
            <link>https://medium.com/@bhaskar.685.vikas/10-linux-error-messages-that-read-like-passive-aggressive-notes-01fe0631fc36?source=rss-cbefb173b6ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/01fe0631fc36</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Bhaskar  Vikas]]></dc:creator>
            <pubDate>Wed, 02 Sep 2026 13:31:00 GMT</pubDate>
            <atom:updated>2026-09-02T13:31:00.975Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lj8UYZmQYe5YuMw0NuB0MA.png" /></figure><h3>Your terminal isn’t angry. It’s just disappointed in you.</h3><p>There’s a very specific emotional experience that comes from breaking something in Linux. It’s not the sharp sting of a Windows blue screen, and it’s not the smug, sanitized apology of a Mac. No — Linux error messages have a personality all their own. They’re calm. They’re precise. And somehow, they always sound like they’re one sentence away from adding “…just saying” at the end.</p><p>If you’ve spent any real time in a terminal, you know the feeling. You didn’t just get an error. You got <em>judged.</em></p><p>Here are 10 Linux error messages that read less like system diagnostics and more like sticky notes left on the office fridge by someone who is absolutely not mad, they just think it’s <em>interesting</em> that you’d do that.</p><h3>1. Permission denied</h3><p>Short. Cold. Final. No explanation, no context, just two words that hit like a roommate silently sliding your name off the chore chart. You didn’t even get a “why.” You’re just denied, and you’re expected to sit with that.</p><h3>2. No such file or directory</h3><p>This one has a special way of making you doubt your own memory. You <em>know</em> the file is there. You made it five minutes ago. But Linux just shrugs and says it simply doesn’t exist, the same energy as someone saying “I never got that email” when you both know they did.</p><h3>3. command not found</h3><p>The terminal equivalent of someone repeating your name back to you with a confused tilt of the head, like you just spoke a language you invented on the spot. It’s not going to guess what you meant. It’s not going to suggest alternatives. It’s just going to sit there, letting the silence make you feel small.</p><h3>4. Segmentation fault (core dumped)</h3><p>This is the tech support version of someone calmly closing a laptop mid-sentence and walking away. No further detail. No stack trace you can actually use half the time. Just total, immediate withdrawal from the conversation — and yes, it left a mess on its way out.</p><h3>5. Operation not permitted</h3><p>Slightly more formal than “Permission denied,” which somehow makes it worse. It’s the difference between a friend saying “no” and a friend saying “that will not be possible at this time.” You can practically hear the clipboard being tapped.</p><h3>6. Disk quota exceeded</h3><p>The digital equivalent of a passive-aggressive note on shared refrigerator leftovers: “This space was for everyone, and you knew that.” You didn’t get a warning as you approached the limit. You just got shut down the moment you crossed it, like your storage had been quietly counting the whole time.</p><h3>7. Killed</h3><p>One word. No punctuation. No process ID sympathy. No “sorry for the inconvenience.” Just the system reaching over, ending your program’s entire existence, and returning to what it was doing, like nothing happened. It’s the conversational equivalent of someone hanging up mid-sentence without raising their voice.</p><h3>8. fatal: not a git repository (or any of the parent directories): .git</h3><p>This is Git’s way of saying, “I don’t know you, I don’t know this place, and honestly, I’m not sure you know where you are either.” It’s technically accurate and somehow still condescending, especially when you <em>know</em> you’re in the right folder and it just won’t validate you.</p><h3>9. Address already in use</h3><p>The programming version of showing up to a parking spot someone else’s car is already sitting in — except the other car is invisible, silent, and apparently more important than your plans. The system won’t tell you who’s squatting there. It just wants you to know that it’s occupied, and that’s your problem now.</p><h3>10. Broken pipe</h3><p>Vague, slightly dramatic, and somehow always your fault even when it isn’t. It’s the system equivalent of someone saying “well, this isn’t working anymore” and refusing to elaborate on what “this” even was. No further explanation offered. You’re just left standing there, holding a pipe that is, apparently, broken.</p><h3>Why Linux talks like this</h3><p>None of this is actually personal — these messages come from decades-old Unix philosophy that values brevity over hand-holding. The system assumes you know what you’re doing, so when something breaks, it doesn’t cushion the blow. It just states the fact and moves on, the same way a very competent, very unbothered coworker might.</p><p>The result is a terminal that never yells, never explains itself twice, and never, ever apologizes — but somehow always makes you feel like you were the one who messed up. Which, to be fair, you probably were.</p><p><strong>Which one hits closest to home?</strong> Tell me in the comments 👇</p><p>Enjoyed this? Clap 👏, follow for more nerd humor, and subscribe so you don’t miss the next one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=01fe0631fc36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Ran sudo rm -rf / So You Don't Have To (A Cautionary Comedy)]]></title>
            <link>https://medium.com/@bhaskar.685.vikas/i-ran-sudo-rm-rf-so-you-dont-have-to-a-cautionary-comedy-a37133736725?source=rss-cbefb173b6ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/a37133736725</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Bhaskar  Vikas]]></dc:creator>
            <pubDate>Wed, 02 Sep 2026 06:11:00 GMT</pubDate>
            <atom:updated>2026-09-02T06:11:00.861Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ehmkaHq510zImnRVwa89Jw.png" /></figure><h3>A love letter to my dead operating system</h3><p>There’s a special kind of silence that happens right after you press Enter on a command you already regret. It’s not quite panic yet. It’s more like the calm before your entire digital life quietly walks itself into the sea.</p><p>That silence is what greeted me the day I typed sudo rm -rf / into my terminal.</p><p>Not as a joke. Not as a meme. On purpose. In a virtual machine, for science, but still — on purpose. And somehow, it still managed to humble me.</p><p>Here’s what happened, why it’s funny, and why you should never, ever do this on a machine you actually care about.</p><h3>First, a quick translation for the civilians</h3><p>If you don’t speak fluent nerd, let me break down this beautiful little string of digital self-destruction:</p><ul><li><strong>sudo</strong> — &quot;Please, computer, let me do something dangerous, I promise I know what I&#39;m doing.&quot; (You do not.)</li><li><strong>rm</strong> — Remove. Delete. Yeet into the void.</li><li><strong>-rf</strong> — &quot;Recursive&quot; and &quot;force.&quot; Translation: delete this thing, and everything inside it, and don&#39;t ask me twice.</li><li><strong>/</strong> — The root directory. Not <em>a</em> folder. <em>The</em> folder. The one everything else lives inside of, like a Russian nesting doll made entirely of your hopes and dreams.</li></ul><p>Put it together and you’re telling your computer: “Delete literally everything, recursively, with extreme prejudice, and don’t bother asking permission.” It’s the digital equivalent of handing someone a lit match and the deed to your house at the same time.</p><h3>The moment of truth</h3><p>I typed it. I stared at it. It looked so calm sitting there in the terminal, blinking at me like it hadn’t just agreed to end everything.</p><p>I hit Enter.</p><p>For about half a second, nothing happened, which is somehow the most terrifying part. It’s the horror-movie pause before the jump scare. Your brain has just enough time to whisper, <em>“wait — “</em> before the screen starts scrolling.</p><p>Then it began: a quiet, relentless stream of text, calmly reporting the deletion of files I didn’t even know existed. Config files. Log files. Fonts. Font files I have never once thought about being deleted, and yet there they went, one by one, like tiny digital soldiers walking off a cliff in formation.</p><p>It felt less like destruction and more like watching a very polite, very thorough Viking raid.</p><h3>What actually dies (and in what order)</h3><p>Modern Linux systems have gotten slightly better at protecting you from yourself — some versions of rm will refuse to run this on / without an extra flag, because apparently even software has trust issues now. But assuming you clear that hurdle, here&#39;s roughly what you&#39;re saying goodbye to:</p><ol><li><strong>Your shell itself.</strong> The very program interpreting your command starts vanishing mid-command. It’s like firing a gun that also shoots you.</li><li><strong>System binaries.</strong> ls, cd, grep — the basic vocabulary of the terminal — all deleted. Your computer forgets how to do anything, including tell you what it just did.</li><li><strong>Boot files.</strong> The instructions your machine uses to wake up in the morning. Gone. Your computer now has permanent amnesia.</li><li><strong>Everything else.</strong> Documents, photos, that one script you wrote in 2019 that you were definitely going to clean up eventually. All of it, unceremoniously erased.</li></ol><p>The whole process usually grinds to a halt once the deletion tools required to keep deleting things have themselves been deleted. Your computer, in a stunning moment of self-awareness, essentially says: <em>“I would love to keep destroying myself, but I no longer have the tools to do so,”</em> and quietly gives up.</p><h3>The aftermath</h3><p>What you’re left with is a machine that boots into a black screen, or a kernel panic, or sometimes just… nothing. No error. No drama. Just the void, humming softly.</p><p>It’s oddly peaceful, in the way a crime scene is peaceful once everyone involved has left.</p><p>I rebuilt the VM in about ten minutes. Real recovery from an actual production machine, on the other hand, usually involves words like “backup,” “downtime,” and “why didn’t we test this in staging,” followed by a very uncomfortable meeting.</p><h3>Why this joke never dies (unlike your files)</h3><p>sudo rm -rf / has become the terminal equivalent of the &quot;big red button&quot; trope — it&#39;s the go-to prank suggestion for messing with new Linux users, the punchline in a thousand programmer memes, and a rite of passage that most sysadmins have either witnessed or narrowly avoided.</p><p>Part of the humor is the sheer elegance of it. Four words. Total annihilation. No hacking skills required, no elaborate malware, no dramatic movie hacking montage — just a person, a keyboard, and a catastrophic lack of hesitation.</p><p>It’s the digital version of Chekhov’s gun, except the gun is loaded, pointed at your own foot, and someone in a forum somewhere is telling you it’s “totally safe, trust me.”</p><h3>The actual lesson here</h3><p>Behind the joke is a genuinely useful reminder: <strong>the terminal does exactly what you tell it to, immediately, and without judgment.</strong> It will not stop to ask “are you sure?” It will not raise an eyebrow. It trusts you completely, which is either beautiful or terrifying depending on the day.</p><p>A few real takeaways, disguised as comedy:</p><ul><li><strong>Never run commands you don’t fully understand</strong>, especially ones involving sudo, wildcards, or the letter combination -rf.</li><li><strong>Back up your stuff.</strong> Not “I’ll get to it” backups. Actual, automated, “future me will thank present me” backups.</li><li><strong>Test destructive commands in a VM or sandbox first</strong>, the way I did — mostly so you can write a blog post about it later instead of filing an incident report.</li><li><strong>If a forum post tells you to run a command “for fun,” be suspicious.</strong> That’s usually rule number one of the internet’s oldest prank.</li></ul><h3>Final thoughts from beyond the grave (of my VM)</h3><p>I ran sudo rm -rf / so you don&#39;t have to, and I regret nothing except my font files, my shell history, and briefly, my life choices. It was fast, it was merciless, and it was — against all odds — kind of beautiful in its efficiency.</p><p>So consider this your public service announcement, delivered with love from someone who has stared into the void of a self-deleted operating system: respect the terminal, question every sudo, and maybe, just maybe, keep your backups closer than your sense of humor.</p><p><em>Now if you’ll excuse me, I have a virtual machine to rebuild. Again.</em></p><p><strong>Got a terminal horror story of your own?</strong> Drop it in the comments — misery loves company, and so do I.</p><p>If this made you laugh (or wince), give it a clap 👏, follow me for more posts where nerds laugh at their own chaos, and subscribe so you don’t miss the next one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a37133736725" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cybersecurity 101: A Beginner’s Guide to Ethical Hacking]]></title>
            <link>https://medium.com/@bhaskar.685.vikas/cybersecurity-101-a-beginners-guide-to-ethical-hacking-ecb9693cc555?source=rss-cbefb173b6ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecb9693cc555</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Bhaskar  Vikas]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 15:44:28 GMT</pubDate>
            <atom:updated>2026-08-31T15:44:28.128Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Understanding how “good hackers” protect the digital world — and how you can start learning the craft.</em></p><h3>Introduction</h3><p>Every time you hear about a data breach, a leaked password database, or a ransomware attack crippling a hospital, there’s a flip side to that story that rarely makes headlines: the ethical hackers working around the clock to prevent exactly those disasters.</p><p>Ethical hacking — also called “white hat” hacking or penetration testing — is the practice of legally probing systems, networks, and applications for vulnerabilities before criminals find them first. It’s one of the fastest-growing career paths in tech, and you don’t need a computer science degree to get started. You need curiosity, patience, and a willingness to think like an attacker in order to defend like a professional.</p><p>This guide walks you through the fundamentals: what ethical hacking actually is, the different types of hackers, the core methodology, essential skills, and how to start learning — legally and safely.</p><h3>What Is Ethical Hacking?</h3><p>Ethical hacking is the authorized practice of bypassing system security to identify potential data breaches and threats in a network. The key word is <em>authorized</em>. An ethical hacker has explicit permission from the system owner to attempt to break in, and their goal is to report vulnerabilities so they can be fixed — not to exploit them for personal gain.</p><p>Companies hire ethical hackers (sometimes called penetration testers or pentesters) to:</p><ul><li>Find weaknesses before criminals do</li><li>Test how well their defenses hold up under real attack conditions</li><li>Meet compliance requirements (like PCI-DSS, HIPAA, or ISO 27001)</li><li>Validate that patches and security controls actually work</li></ul><p>Think of it like hiring someone to try to break into your house — with your permission — so they can tell you exactly which window doesn’t lock properly.</p><h3>The Hats of Hacking: Know the Difference</h3><p>You’ll often hear hackers categorized by “hat color.” It’s a simple but useful framework:</p><ul><li><strong>White Hat</strong> — Ethical hackers who work with permission to improve security.</li><li><strong>Black Hat</strong> — Criminal hackers who exploit systems for personal gain, causing harm.</li><li><strong>Grey Hat</strong> — Hackers who may break into systems without permission but without malicious intent, often disclosing flaws afterward. This is a legal gray area and generally discouraged.</li><li><strong>Red Team / Blue Team</strong> — In corporate settings, red teams simulate attackers while blue teams defend. Some organizations also run “purple team” exercises where both sides collaborate.</li></ul><p>If you’re learning ethical hacking, your goal is to operate exclusively in white hat territory: proper authorization, clear scope, and legal boundaries at all times.</p><h3>The Core Methodology: How Ethical Hackers Work</h3><p>Most penetration tests follow a structured process. Understanding this framework will help you think like a professional from day one.</p><h3>1. Reconnaissance (Information Gathering)</h3><p>Before touching a system, hackers gather as much information as possible — domain names, IP ranges, employee names, technologies in use. This can be <em>passive</em> (using public information like search engines, social media, and WHOIS records) or <em>active</em> (directly probing the target’s systems).</p><h3>2. Scanning</h3><p>Here, testers use tools to identify live hosts, open ports, and running services. This is where you start mapping the attack surface — essentially figuring out which doors and windows exist.</p><h3>3. Gaining Access</h3><p>Using the information gathered, the tester attempts to exploit identified vulnerabilities to gain access to the system. This might involve weak passwords, unpatched software, or misconfigurations.</p><h3>4. Maintaining Access</h3><p>Real attackers often try to stay inside a system undetected for as long as possible. Ethical hackers simulate this to test how well an organization can detect and respond to a persistent threat.</p><h3>5. Covering Tracks (and Reporting)</h3><p>Malicious hackers erase evidence of their presence. Ethical hackers do the opposite: they document everything meticulously and deliver a detailed report outlining what they found, how they found it, and how to fix it.</p><p>This structured approach — sometimes called the “Cyber Kill Chain” or mapped against frameworks like MITRE ATT&amp;CK — is the backbone of professional penetration testing.</p><h3>Essential Skills for Beginners</h3><p>You don’t need to master everything at once, but here’s what to prioritize:</p><p><strong>Networking fundamentals</strong> — Understand how data moves: IP addresses, DNS, TCP/UDP, firewalls, and the OSI model. You can’t secure what you don’t understand.</p><p><strong>Operating systems</strong> — Get comfortable with both Windows and Linux, especially the command line. Linux, particularly distributions like Kali Linux, is the standard environment for security tools.</p><p><strong>Scripting and programming</strong> — You don’t need to be a software engineer, but basic Python or Bash scripting goes a long way for automating tasks and understanding exploits.</p><p><strong>Web technologies</strong> — HTTP/HTTPS, cookies, sessions, and how web applications communicate are foundational, since web app vulnerabilities are among the most common findings in the field.</p><p><strong>Understanding common vulnerabilities</strong> — Familiarize yourself with concepts like SQL injection, cross-site scripting (XSS), and misconfigurations. The <strong>OWASP Top 10</strong> is the industry-standard starting point for web application security risks.</p><h3>Legal and Ethical Boundaries (Non-Negotiable)</h3><p>This can’t be overstated: unauthorized access to computer systems is illegal in virtually every country, regardless of intent. Laws like the Computer Fraud and Abuse Act (CFAA) in the U.S. carry serious criminal penalties.</p><p>Before you test <em>anything</em>, make sure you have:</p><ul><li><strong>Written authorization</strong> — A signed agreement or clearly defined scope from the system owner.</li><li><strong>Defined scope</strong> — Know exactly what you’re allowed to test and what’s off-limits.</li><li><strong>A rules of engagement document</strong> — Outlining timing, methods, and reporting expectations.</li></ul><p>If you’re practicing on your own, only test systems you own or platforms explicitly built for legal practice (more on that below). Never test a system “just to see” without permission — even with good intentions, this can lead to serious legal consequences.</p><h3>How to Start Learning: Safe, Legal Practice Grounds</h3><p>The good news is that you never have to break the law to build real skills. There’s an entire ecosystem built for hands-on, legal practice:</p><ul><li><strong>TryHackMe</strong> and <strong>Hack The Box</strong> — Gamified, beginner-friendly platforms with guided labs covering everything from basic networking to advanced exploitation.</li><li><strong>OWASP Juice Shop</strong> and <strong>DVWA (Damn Vulnerable Web Application)</strong> — Intentionally vulnerable applications you can run locally to practice web hacking.</li><li><strong>PicoCTF</strong> — A beginner-oriented Capture the Flag competition originally built for high schoolers, great for building fundamentals.</li><li><strong>Bug bounty programs</strong> — Platforms like HackerOne and Bugcrowd let you legally test real companies’ systems (within defined scope) and get paid for valid findings.</li></ul><p>Building a home lab using virtual machines is also a great low-cost way to practice safely and destructively — you can break things in a VM without any real-world consequences.</p><h3>Certifications Worth Knowing About</h3><p>As you progress, certifications can validate your skills and open career doors:</p><ul><li><strong>CompTIA Security+</strong> — A solid entry-level foundation in general cybersecurity.</li><li><strong>CEH (Certified Ethical Hacker)</strong> — Widely recognized, covers broad hacking methodology.</li><li><strong>OSCP (Offensive Security Certified Professional)</strong> — Highly respected, hands-on, and considered a benchmark for practical penetration testing skill.</li><li><strong>CompTIA PenTest+</strong> — A solid intermediate step focused specifically on penetration testing.</li></ul><p>You don’t need every certification — pick a path based on the career direction you want (network security, web app security, cloud security, etc.).</p><h3>Final Thoughts</h3><p>Ethical hacking isn’t about being a mysterious hoodie-wearing figure typing furiously in a dark room — it’s a disciplined, methodical profession built on curiosity, continuous learning, and a strong ethical compass. The same skills that let someone break into a system are the skills that let organizations defend themselves against real threats.</p><p>If you’re just starting out, focus on the fundamentals: networking, operating systems, and the OWASP Top 10. Practice exclusively on legal platforms. Stay curious, stay patient, and always remember — the “ethical” in ethical hacking is the whole point.</p><p>The digital world needs more defenders. This might be where you start.</p><p><em>If you found this useful, follow for more beginner-friendly breakdowns of cybersecurity concepts, tools, and career paths.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecb9693cc555" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nmap for Beginners: 10 Commands You Need to Know]]></title>
            <link>https://medium.com/@bhaskar.685.vikas/nmap-for-beginners-10-commands-you-need-to-know-d2be8df700b3?source=rss-cbefb173b6ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2be8df700b3</guid>
            <category><![CDATA[nmap]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Bhaskar  Vikas]]></dc:creator>
            <pubDate>Sun, 30 Aug 2026 09:58:09 GMT</pubDate>
            <atom:updated>2026-08-30T09:58:09.589Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re just getting into networking or cybersecurity, you’ve probably heard people talk about Nmap. It sounds intimidating at first — like something only hackers in movies use. But honestly, once you get past the first few commands, it’s not that scary. It’s just a tool that tells you what’s happening on a network.</p><p>I remember when I first opened a terminal and typed nmap with no idea what to do next. So this post is basically the guide I wish someone had handed me back then. No jargon overload, just the commands that actually matter when you&#39;re starting out.</p><h3>What Even Is Nmap?</h3><p>Nmap (short for Network Mapper) is a free tool used to scan networks and find out what devices are connected, what ports are open, and what services are running on them. System admins use it to check their own networks for weak spots. Security folks use it to test systems before attackers do. It’s one of those tools that shows up in almost every “how to learn cybersecurity” list, and for good reason.</p><p>One thing before we jump in — only scan networks and devices you own or have permission to test. Scanning random networks without permission can get you in legal trouble, so keep it to your home lab, a test environment, or systems you’re authorized to check.</p><h3>1. Basic Scan</h3><pre>nmap 192.168.1.1</pre><p>This is the simplest command there is. Point it at an IP address and it’ll tell you which ports are open on that device. It’s a good first step whenever you’re checking a machine.</p><h3>2. Scan a Range of IPs</h3><pre>nmap 192.168.1.1-50</pre><p>Instead of checking one device at a time, this scans a whole range. Useful if you want to see everything connected across a chunk of your network at once.</p><h3>3. Scan an Entire Subnet</h3><pre>nmap 192.168.1.0/24</pre><p>This covers every device on that subnet, all 254 possible addresses. It’s a fast way to get a full picture of what’s alive on your network right now.</p><h3>4. Scan Specific Ports</h3><pre>nmap -p 80,443 192.168.1.1</pre><p>Sometimes you don’t need to check every port, just the ones you care about. This example only checks port 80 (HTTP) and 443 (HTTPS).</p><h3>5. Scan All 65,535 Ports</h3><pre>nmap -p- 192.168.1.1</pre><p>By default, Nmap only checks the most common 1,000 ports. If you want the full picture, this checks every single port. It takes longer, but it’s more thorough.</p><h3>6. Detect the Operating System</h3><pre>nmap -O 192.168.1.1</pre><p>This one tries to guess what OS the target machine is running — Windows, Linux, macOS, whatever. It’s not always 100% accurate, but it’s a handy starting point when you’re trying to understand a device you don’t recognize.</p><h3>7. Detect Service Versions</h3><pre>nmap -sV 192.168.1.1</pre><p>Knowing a port is open is one thing. Knowing what software is actually running behind it is another. This command tries to identify the version of the service, like whether it’s an old version of Apache or a newer one. Older versions are usually more vulnerable, so this is a big one for security checks.</p><h3>8. Aggressive Scan</h3><pre>nmap -A 192.168.1.1</pre><p>This is like the “give me everything” option. It combines OS detection, service version detection, script scanning, and traceroute all in one go. Great for getting a detailed report quickly, but it’s noisier and slower than a basic scan.</p><h3>9. Save Results to a File</h3><pre>nmap -oN results.txt 192.168.1.1</pre><p>When you’re scanning multiple devices or doing this regularly, you don’t want to lose your results. This saves the scan output to a text file so you can look back at it later or share it with someone.</p><h3>10. Skip the Ping Check</h3><pre>nmap -Pn 192.168.1.1</pre><p>By default, Nmap tries to ping a device first to check if it’s online before scanning it. But some devices are set up to ignore pings even though they’re active. This command skips that check and scans anyway, which is handy when you know a device is up but Nmap thinks otherwise.</p><h3>Putting It All Together</h3><p>You don’t need to memorize all of these right away. Start with a basic scan, get comfortable with it, then slowly add options as you need them. A command like:</p><pre>nmap -sV -O -p- 192.168.1.1</pre><p>is really just combining a few things you already learned — service detection, OS detection, and a full port scan — into one line.</p><h3>Final Thoughts</h3><p>Nmap has way more features than what’s covered here. There are scripts, timing options, stealth scans, and a whole world beyond these ten commands. But you don’t need all of that on day one. Learn these, practice on your own network or a lab setup, and the rest will start making sense naturally.</p><p>The best way to actually learn this stuff is to just open a terminal and try it. Set up a small home network or a virtual lab, run these commands, and see what comes back. That’s how it clicked for me, and it’ll probably work the same way for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2be8df700b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 Funny Linux Commands That Prove Nerds Have a Sense of Humor Too]]></title>
            <link>https://medium.com/@bhaskar.685.vikas/8-funny-linux-commands-that-prove-nerds-have-a-sense-of-humor-too-5ccf138813fd?source=rss-cbefb173b6ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ccf138813fd</guid>
            <category><![CDATA[terminal]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[kali-linux]]></category>
            <dc:creator><![CDATA[Bhaskar  Vikas]]></dc:creator>
            <pubDate>Thu, 27 Aug 2026 18:21:08 GMT</pubDate>
            <atom:updated>2026-08-27T18:21:08.419Z</atom:updated>
            <content:encoded><![CDATA[<p>Linux has a reputation for being cold, serious, and allergic to fun. Black terminal windows. Cryptic flags. People who argue about text editors like it’s a religious war.</p><p>But dig a little deeper into the terminal, and you’ll find that the people who built this operating system have a delightfully weird sense of humor. Buried inside package repositories and open-source projects are commands that exist purely to make you laugh, confuse your coworkers, or prank the next person who sits down at your desk.</p><p>Here are 8 commands that prove even the nerdiest corners of tech have a funny bone.</p><h3>1. sl — For When You Fat-Finger ls</h3><p>Everyone has typed sl instead of ls at least once. Normally, that just gets you a &quot;command not found&quot; error. But if you install the sl package, mistyping ls summons a full ASCII-art steam locomotive that chugs across your screen.</p><pre>sudo apt install sl<br>sl</pre><p>It serves no purpose whatsoever. It won’t list your files. It exists purely to punish — or reward — your typos with a train.</p><h3>2. cowsay — Wisdom, Courtesy of a Cow</h3><p>cowsay takes any text you give it and puts it in a speech bubble coming out of an ASCII cow.</p><pre>cowsay &quot;Why did the terminal cross the road?&quot;</pre><p>The result is a small bovine philosopher staring back at you from your terminal. There are variations too — cowsay -f dragon, cowsay -f tux — because apparently one animal wasn&#39;t enough.</p><h3>3. fortune — A Fortune Cookie for Your Command Line</h3><p>Running fortune spits out a random quote, joke, or piece of trivia, just like cracking open a fortune cookie.</p><pre>fortune</pre><p>On its own it’s mildly amusing. Combined with cowsay, it becomes a full comedy act:</p><pre>fortune | cowsay</pre><p>Now a cow is giving you your daily dose of wisdom. Truly the pinnacle of software engineering.</p><h3>4. cmatrix — Become a Hacker in Under 5 Seconds</h3><p>Want to look like you’re breaching mainframe security in a 90s hacker movie? cmatrix fills your terminal with the green falling code straight out of <em>The Matrix</em>.</p><pre>sudo apt install cmatrix<br>cmatrix</pre><p>It does nothing productive. It just looks incredible on a second monitor when your coworkers walk by.</p><h3>5. sudo apt-get moo — The Easter Egg Nobody Tells You About</h3><p>Debian and Ubuntu’s package manager, apt-get, has a hidden joke baked right in. Type this exactly:</p><pre>sudo apt-get moo</pre><p>You’ll be greeted by an ASCII cow saying: <em>“Have you mooed today?”</em> It’s a tiny, pointless easter egg — and that’s exactly why it’s great.</p><h3>6. telnet towel.blinkenlights.nl — Star Wars, But Make It ASCII</h3><p>This one is a piece of internet legend. Run this command:</p><pre>telnet towel.blinkenlights.nl</pre><p>And you’ll be treated to the entire opening of <em>Star Wars Episode IV</em> reenacted in ASCII art, streamed live over Telnet. It’s been running since the early 2000s, and it still works — proof that some corners of the internet never die.</p><h3>7. yes — The Most Aggressively Agreeable Command Ever Made</h3><p>yes is supposed to be a utility for automating confirmation prompts, but running it with no arguments just floods your terminal with an infinite stream of the word &quot;y&quot;:</p><pre>yes</pre><p>It will keep saying yes until you force it to stop (Ctrl+C). Want it to really commit to a bit?</p><pre>yes &quot;I will not procrastinate today&quot;</pre><p>Now your terminal is gaslighting you into productivity, one line at a time.</p><h3>8. xeyes — Googly Eyes for Your Desktop</h3><p>xeyes opens a small window with a pair of cartoon eyes that follow your mouse cursor around the screen.</p><pre>sudo apt install x11-apps<br>xeyes</pre><p>It’s unsettling, pointless, and somehow endlessly satisfying to move your mouse around just to watch the eyes track it.</p><h3>Why Do These Commands Even Exist?</h3><p>Because programmers get bored, and the terminal is basically the world’s driest canvas. Somewhere along the way, someone decided that if you’re going to spend 8 hours a day staring at a black screen full of text, you might as well be able to summon a cow, a train, or a Star Wars marathon while you’re at it.</p><p>So next time someone tells you Linux users are humorless keyboard warriors, just open a terminal, type sudo apt-get moo, and let the cow do the talking.</p><p><em>Got a favorite weird or funny terminal command? Drop it in the comments — the nerdier, the better.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ccf138813fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>