New Linux users diving headfirst into Kali's dark penetration-testing cave
Description
Meme with a white header that reads, "NO ONE:" (nothing follows) and beneath it "NEW LINUX USERS:" in bold black capitals. The main image shows an outdoor scene: a bearded person wearing a wide-brimmed straw hat, teal long-sleeve shirt, and backpack stands at a rocky cave entrance, face intentionally obscured. Their left hand gestures toward the darkness. Over the cave mouth floats the blue-circle Kali Linux logo featuring a white stylized dragon. A subtitle along the bottom says, "I've got no idea why, but I'm goin' in there!" The humor plays on newcomers to Linux impulsively installing an advanced security distribution (Kali) despite lacking context - highlighting operating-system curiosity, command-line experimentation, and the allure of penetration-testing tools
Comments
23Comment deleted
Watching a new hire dual-boot Kali on their daily driver and plug it straight into the prod VPN is the DevSecOps equivalent of spelunking with fireworks - sure, they’ll learn something, but so will the incident-response team
Twenty years later, they're still in there, maintaining a custom kernel they compiled in 2004 because switching distros would mean admitting the wiki didn't prepare them for systemd
Ah yes, the classic 'I installed Kali as my daily driver' starter pack. Nothing says 'I understand privilege escalation' quite like running every application as root because you haven't figured out sudo yet. It's the cybersecurity equivalent of buying a Formula 1 car before learning to drive stick - technically impressive hardware, but you're still going to stall it in the Starbucks parking lot while trying to crack your own WiFi password
Like proposing a monorepo refactor to a legacy COBOL team: zero clue on fallout, but the wiki's your parachute - if you RTFM first
Choosing Kali to learn Linux is the desktop equivalent of spinning up a public k8s cluster to learn YAML - sure, you’ll learn; the incident report writes itself
Rookies sprint into Kali like it’s a tunnel to root; the rest of us keep it in a disposable VM because the day DKMS can’t find your kernel headers, your Wi-Fi becomes air-gapped by accident
That's because of will of being mothers hackerman, when you have no idea how to grep logs Comment deleted
'of cource i do its just cat | grep' Comment deleted
an obvious mistake: not using ripgrep in 2022 Comment deleted
an obvious mistake: thinking something is better just because it's newer Comment deleted
It's not about being newer but faster while having more batteries included. Comment deleted
I really doubt it's faster & it's also 5 times the size of grep Comment deleted
damn, how can a PC user find more than 15 kb of free memory in 2022 Comment deleted
all I'm saying is that whatever ripgrep is, it's not better for all use-cases Comment deleted
I dunno, I use import file_tree, for file in file_tree Comment deleted
It runs circles around GNU grep in pretty much every case. Even when you manually whitelist files which ripgrep does by default e.g. in git repos (the batteries, y'know). x2.5 the size (Debian Stable amd64) because you forgot to count libpcre Comment deleted
both grep and ripgrep depend on libpcre, so it shouldn't count towards package size Comment deleted
https://packages.debian.org/bullseye/ripgrep 😁 PCRE2 is optional in ripgrep Comment deleted
not on arch linux Comment deleted
cuz it’s free Comment deleted
Linux users after that be like: Comment deleted
The real new linux users be like: Ubuntu, Mint, Zorin Comment deleted
What is wrong tho Comment deleted