a perfect place to launch a full-blown attack on one of the gov services

damn
that was AMS (accidental message send)

spent a decent time writing that, which was actually meant for a different use case (shouldn't be exposed publicly) and ended up here. i should sort out my folder's shit. anyways, this can be a good referencing material to the post (took some ideas from it)

got this script i was writing. been a while actually since i wrote one with python and i was just thinking to switch to go. the Arch package repository is a bit different from kali. I kinda gotta do a manual package repository mapping from kali to arch (got a kali tools python list consisting pretty much every tool) or the other way around is to prepare another list only for Arch official repo and AUR packages after making sure they actually exist. if not, adding independent repositories for each of them might work.

speaking of perl, i was kinda taking a look at old scripts and quite a lot of them used to write their scripts with perl. Facemash was a good example. here goes the young, dumb and broke Zuck

if an attacker is on your network, his other computer is your computer

apparently most of modern cars are vulnerable through a license plate. there was specifically a python 3 script written by Neiko to compromise KIA automobile (actually pretty much most vehicles). the snapshot was smh visible to the BBP hunters meetup in Vegas. turns out KIA cars are also vulnerable through the KIAtool app (it has been a disclosed vulnerability publicly after validating on September 26 last year)

for my hardcore nerds:

https://t.me/mira_files/105

> tells a bro to give me his MAC address to whitelist it on the router
> replies "i use hp"

gotta be honest, the hacker community is harsh. dunno much about the local communities, but the ones i experienced before are way harsher. the DEF CON peeps are somehow welcoming. the one yapping nonsense and filled with too much ego are full of crap. hack a car; they call you a noob, do binary exploitation; they call you a noob, find a bug on a source code; they call you a noob. that's when the imposter syndrome kicks in. in fact, there are many communities with a positive vibe, but the toxic ones keep coming up. well, the best thing to do in order to avoid that is to literally ignore them and focusing only on your own skills. at the end of the day, you get your paycheck either defending a system or breaking in. the other way around is shadier and too deep.

tl;dr focus on progressing rather than a nonsense opinion of someone. if you wanna end up stagnant, ask everyone for their advice.

tl;dr tl;dr hone your skills in spite of toxic situation

Tip of the day I learned:
Start every phone call with
"my phone is about to die" then you can hang up whenever you want.

The fact that people are becoming aware of UX gives an idea for local products

me: sigh, this flag is hard to capture (and yes started playing CTFs)

progress craving inner voice: your actual progress is not how hard you worked till you get tired; it's how long you will work after you get tired.

[Setun]