I always say “I’m in” when remote connecting or remembering a stupid password or whatever but none of my coworkers get it because they’re not anglophones.

I usually just mutter “finally”, possibly prefixed with an explative.

Hack the Planet!

No. But I once mumbled “What, they left it open?”

Also, I lol’d a bit when I ran John on a password file I lifted from a school server. Turned out this girl I know had her password set to “Urine”. And, no, I neither cared nor used it. I just found that nugget a bit funny.

I do, however, frequently declare “I’m in” when logging in to work while I have someone on the phone - The remote systems are on extremely lagging and unreliable VSAT, so even though I’m supposed to remote in relatively often, it’s not a given that a simple SSH connection will work.

I do this with my own stuff. I dug out a few hard drives that were gibberish because they were in a RAID array at one point. I put them all in a Linux machine and eventually found the right command to make them work. I definitely muttered, “I’m in…”

I open a can of jolt cola every time I get in. That’s why I’m so fat.

I usually say, “Nice try, FBI.”

I usually say: “ARE YOU A FUCKING FED. TELL ME NOW”

No, but I have leaned back in my char and cracked my knuckles.

Of all the fake things you see on tv about hackers, that part is real.

Every time. Your mom’s getting tired of me saying it.

Yes. Most of them were east-to-find solutions on the web, or someone else giving me access. “Can you reset my password on Blah?” “Try TempP@ass123.” “I’m in, changed password. Thanks.”

A few times when I am really acting like a Senior Linux Administrator is figuring out a kludge or back door nobody had thought of. Recently, a client told me that the former admin had left and didn’t leave the password to over 300 systems (it turns out he did, the client was clueless, but I didn’t know that in the moment). I found every system the admin had access to, and looked for a dev box where he had access but I could take down during production hours. I took it down, booted into init with /bin/bash, changed root password, brought it back up. Then I checked his home directory to see what public keys he had. Based on that, I checked to see if there were any private keys on the bastion systems that matched as a pair (using ssh-keygen -l -f on each pair to see if the signatures matched). They checked which pair had no password. That was pretty quick because I quickly discovered a majority of these cloud systems also had an ec2-user that could escalate to root via private/public key pairs (it is supposed to be removed for security reasons, but wasn’t). Within a few hours, I had full access back to all their systems. Without taking down production.

Even if you don’t say it, oh you’ll feel it. Even if you’re just dicking around on your own network and exploit something from a guide as practice…

Yeah, I’m in.

I’ve said both. I’m a professional pentester / red teamer, and yeah, we send each other “I’m in” memes when we pop a box.

“Alright, I’m in now.”