SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY, SECURITY & SAFETY
As an novice whitehat hacker, there are several tasks you can perform using the Command Prompt (CMD) to enhance your cybersecurity knowledge and protect systems. It's important to note that whitehat hacking is focused on ethical and legal practices, ensuring the security and integrity of systems. Here are a few tasks you can explore:
-
Network Diagnostics: Use CMD commands like
ipconfig,ping, andtracertto diagnose network issues, test connectivity, and troubleshoot network problems. -
Security Auditing: Perform basic security audits using commands such as
netstatto identify open ports,tasklistto list running processes, andsysteminfoto gather system information for vulnerability assessment. -
Password Auditing: Utilize tools like
net usercommand to manage user accounts,wmicto retrieve password policy information, andseceditto analyze security policies for password auditing purposes. -
Malware Analysis: Employ CMD tools like
dir,attrib, andtasklistto investigate suspicious files, folders, and processes. Use tools such assfc(System File Checker) to verify the integrity of system files. -
Log Analysis: Analyze event logs using
eventvwrto identify potential security incidents, system errors, or anomalies. -
Scripting and Automation: Learn to write simple batch scripts (.bat files) using CMD commands for automating tasks, such as backups, system monitoring, or routine maintenance.
-
System Administration: Familiarize yourself with CMD commands for user management (
net user), file and folder operations (cd,copy,move, etc.), and system configuration (regedit,gpedit.msc) to better understand system administration tasks.
It's important to note that while using CMD commands, always ensure you have proper authorization and adhere to legal and ethical guidelines. Continuous learning, research, and staying updated with cybersecurity best practices will help you advance your skills and responsibly contribute to maintaining system security.
REM To set up the remote computer to allow remote command executions
reg add HKLM\Software\Microsoft\windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
:: Revert Changes
reg add HKLM\Software\Microsoft\windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 0 /f
%[:%
This command is used to list all the wireless network profiles that have been stored on your Windows computer.
When you run this command, it will display a list of all the Wi-Fi networks that your computer has connected to or tried to connect to in the past.
These profiles can include both secured and open networks.
%:]%
netsh wlan show profiles
%:]%
This command is more specific and is used to display detailed information about a particular wireless network profile, including its security key.
You need to replace "Name" with the name of the network you want to retrieve information about.
When you run this command, it will provide you with the security key (password) of that particular Wi-Fi network, assuming you have the necessary permissions.
%:]%
netsh wlan show profile name="Name" key=clear
:: Check for connections
netstat -ano | findstr "ESTABLISHED"
:: Check who makes that connection
PS C:\Users\danie> tasklist /FI "PID eq 41624"
Image Name PID Session Name Session# Mem Usage
========================= ======== ================ =========== ============
brave.exe 41624 Console 7 57.108 K
:: Get path from processid
wmic process where processid=1337 get ExecutablePath
:: In Wireshark, you could use this filter:
tcp.port == 443 and process.pid == 41624arp.opcode == 2
eth.dst && !(eth.dst[1:2] == eth.dst[3:4] && eth.dst[1:2] == eth.dst[5:6])
// TLS Client Hello
tls.handshake.type == 1
// TLS Server Hello
tls.handshake.type == 2
:: Using the wi-fi for 10 seconds, write it into the file "tshark.pcap"
C:\Program Files\WireShark>tshark -i "wi-fi" -a duration:10 -w tshark.pcap
:: Using the wi-fi for 10 seconds, capture filter is DNS write it into the file "dns.pcap"
C:\Program Files\WireShark>tshark -i "wi-fi" -f "src port 53" -a duration:15 -w dns.pcap
| Layer | Attack | |
|---|---|---|
| 7 | Application | Buffer overflow, XSS, DDoS |
| 6 | Presentation | Unicode vulnerability, SSL strip |
| 5 | Session | Session hijacking, DNS poisoning |
| 4 | Transport | SYN flood, invalid TCP flags, UDP flood |
| 3 | Network | ICMP flood, OS fingerprinting, IP address spoofing, routing table poisoning |
| 2 | Data Link | Sniffing, ARP cache poisoning, macof attack |
| 1 | Physical | Cutting cables, jamming, keystroke logging |
Working with Linux is one of the most confusing, infuriating, and yet strangely rewarding relationships a person can have with a machine.
It’s like falling in love with someone who constantly gaslights you — but then teaches you something profound right after the fight.
At first, you’ll spend hours staring at a terminal window, wondering why something so simple
— like copy-paste, Wi-Fi drivers, or your mousepad — suddenly stops working for no reason.
You’ll reinstall, reconfigure, recompile, and rethink your life choices.
You’ll open 47 tabs with “fix xyz not working on Linux” and end up learning what a kernel module even is
when all you wanted to do was change your wallpaper.
You’ll scream. You’ll swear vengeance. You’ll swear off Linux forever.
Then... you’ll boot it again the next morning. Because you can’t stay away.
There’s a strange beauty in how much Linux forces you to learn.
Every frustration becomes a lesson, every crash a clue, every dependency error
a reminder that you’re building something yourself — not just consuming it.
It’s messy, raw, and often completely irrational.
But so is love.
Eventually, you stop raging and start laughing when things break.
Because you know you will fix it. You always do.
And in those rare, magical moments when everything works perfectly —
when your system is running faster, cleaner, and more tailored than anything corporate software could ever dream of —
you realize why people stay.
Linux doesn’t care if you’re ready.
It doesn’t try to please you.
It throws you into the deep end, watches you sink,
then quietly teaches you how to swim. 🐧💻
So yeah — Linux sucks balls.
But it also builds warriors, thinkers, and problem-solvers out of ordinary users.
And once you get hooked, you’ll never see computers the same way again.
“figure it out, warrior.” 🗡️🐧
“You have all the drawbacks of being part of a megacorp, but you also still have all the drawbacks of being run by a semi-organized community”
