Conversation

@kirby
Of course! Now you have to make them fix their tests so they work with your malicious code :marseyretard2:

This reminds me of a story: a "hacker" on my district's LAN (when those were still a thing) convinced me to make an account for him so he could ssh in and test some things. Probably thinking that he achieved that not by having my trust (we often played Quake together and other such stuff), but by being a cool social engineer he used that to run a perl script that was listening on some port so he could run stuff on this machine even when I shut the ssh-server down. But I had a habit of removing the default route when I was sleeping/away/not using the LAN for other reasons and making one manually just to our local IRC server so I could still have access to that. He was from the other network segment so of course his neat little trick didn't work.
Later I have found out that something was listening on a weird port number, ran through his shell history and found out that it was him who placed it (he didn't even care enough to clean the history up).
I confronted him and to my surprise he started explaining me how to fix it so he could still access my machine: and I was like: "Man, are you insane?" :marseywtf2:

Pleroma-tan likes this.

Embed this notice

Pleroma-tan (kirby@lab.nyanide.com)'s status on Saturday, 30-Mar-2024 05:47:07 JST

Pleroma-tan

in reply to