Linux nerd and consultant. Sci-fi, comedy, and podcast author. Former Katsucon president, former roller derby bouncer. http://punkwalrus.net

  • 1 Post
  • 30 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle



  • Probably HR (or the NCS equivalent) never told the right people. I am not saying this is actually what happened, but a lot of IT bemoan the fact they are never told some rando employee was fired because HR neglects to inform them. Sometimes it takes months to discover, and even with a 90 day password/login lockout, some halfway decent admin could get around this by secretly building a back door, and using the messed up communication and politics between departments to hide this. Even in the 1990s, I saw people put in “time bombs” in their code that “if such and such is not updated in 6 months, run destructo-script A.”

    But imagine someone like Kandula Nagaraju here. Worked in QA, probably did a great jobs with some skills, but had the personality of swallowing broken glass. He was terminated in October 2022 due to “poor work performance,” which could mean anything. “Not a team player.” Or maybe he really was an idiot: I mean, a smart person would have a conniption, but get employed elsewhere and then slam his former company at parties. “Those NCS folks didn’t know what they had with me!” But this guy was probably someone with some anger management issues, probably a jerk, and possibly stupid. He might have had revenge fantasies, and set up a small virtual server posing as a backup code mirror. But outside the audits, it allowed ssh from the outside, and hid it through a knockd daemon. Or maybe only launched ssh at certain hours before shutting it down again. Silently working away in a sea of virtual servers with little to no updated documentation. He gets in, has internal access, and runs a script with admin credentials because they don’t rotate their AWS keys/secrets quickly enough. Or didn’t even know he was let go.

    After Kandula’s contract was terminated and he arrived back in India, he used his laptop to gain unauthorised access to the system using the administrator login credentials. He did so on six occasions between Jan 6 and Jan 17, 2023.

    That’s embarrassing to the company. Not only did he get in, but SIX TIMES after he was let go. he probably knew what order to run the delete commands (like, say, an aws “terminate-instances” cli command from a primary node), and did so one by one, probably during hours with the least amount of supervision, where the first few alerts would take hours to get someone in the monitoring chain to wake an admin. Given his last day was in November, and he got back in January, the admins probably thought their 90 access credential rotation was “good enough,” but he got in on his 80th day or whatever.

    I know this because I have had to do triage when a former contractor did this to a company I worked for. But instead of wiping out instances, he opened a new set of cloud accounts from the master account, put them in an unmonitored region (in this case, Asia), and spun up thousands of instances to run bitcoin mining. Only because AWS notified us of “unusual traffic” were we made aware at all, and this guy knew his shit and covered his tracks very well. He did it at a speed that could have only been automated. Thankfully, AWS did not charge us the seven figure amount that this activity amassed in just three days.



  • Having moderated forums back in the day, I can answer to some of that motivation.

    First, some people are just bullies. A sense of tribalism forms around bullies, who feel the need to act out and repeat the abuses they have endured. Hazing stems from this, too. Cruelty masked as “you should know better,” advice. Given too late.

    Some have a smug sense of superiority, and want to keep it that way. Less smart people means they stay king of the mountain. Others are scared their own lack of knowledge will cripple them if they don’t keep the potential competition down. Insecurities drown out any sense of empathy.

    Some people hate themselves so they punish others in retaliation. Like, trying to erase past cringe by making others hurt to even the score.

    A few are sick of “the same fucking newbie questions again and again and again,” but still hang out in newbie forums for some reason.


  • really just doesn’t do what I needed to do.

    This has been my experience, or sort of does what I want it to do, but I have to rethink what I need it to do instead of something really simple. Like a “new type of shared file system” that replaces NFS/Windows sharing. So instead of files in a standard file system one can manage with a file browser, it has “indexed” your files in such a way that the actual files are renamed into data chunks, and one “finds” files by their non-intuitive search engine that can’t do even basic search engine tricks like “AND/OR” searches, wildcards, and the results are hit and miss. “But it’s faster and more elegant!” So how do you restore from backup when the system fails? “When the system does whatnow?”

    Yeah, no thanks. I can recover files from a file system much easier than some proprietary encoded bullshit fronted with a bad search engine over a proprietary and buggy index.



  • I married my first wife when she was 18 and I was 20. We went through a lot of hardship. It should not have worked out: we were both poor, from broken homes, in an LDR from different worlds. She was the popular girl, I was a shy and awkward nerd. When we got married, we had only been in one another’s presence for a few weeks total. I went into the marriage not expecting a path or plan, as my parents were toxic which ended with my mother’s suicide, and my mother in law had been married 4 times before she became single for the last time. None of us had healthy marriages to draw from. At our wedding, her relatives even said, “I give it two years, tops.” We were desperately poor, and struggled most of our marriage with health and money issues.

    But we made it work for 25 years. We’d still be married, but she passed away ten years ago. We became “foxhole buddies,” us against the world.






  • Having worked for both, I would say that most government offices are eternal, whereas private companies can vanish quickly. Sometimes without warning. Its really hard to kill a government office.

    Makes me wonder, how did a necessary office survive during a junta or an overthrow? For example, how did the office of a postal clerk change from 1925 to 1955 in, say, Berlin? How does the average Salvadoran DMV worker view the changes in El Salvador since 1980?

    How was a tax office run in ancient Babylon versus a modern one today?

    I bet there’s some weird insights into human civilization to be found in those stories.


  • Punkie@lemmy.worldtoMemes@lemmy.mlEconomic Theory is Fun tho.
    link
    fedilink
    arrow-up
    61
    arrow-down
    4
    ·
    11 months ago

    The ironic thing is that they because successful because of civilization and pack mentality, but are so conceited, they think all that infrastructure (public roads, doctors, restaurants, etc) exists simply because they exist. It’s weirdly how toddlers see the universe, and why tantrums between the two groups are so similar.



  • I had a boss who never gave me a raise, didn’t believe in reviews, and had long rambling meetings where he just said whatever he was thinking. Sometimes it seemed he forgot we were there, and he’d start arguing with himself. He was more “the insecure nerd who got the CTO position because he was the only IT guy when the company started.” His management was so incompetent, that they called him “Tallest,” based on the Invader Zim joke.


  • Being poor. In college in the 90s, my lead sysadmin couldn’t afford Minix for this system we had, so we tried to compile Linux on it. Three days later, we still failed, and gave up, but this was kernel 0.93 or something, so it had a ways to go. But I learned so much from that experience without paying for a university course or something.

    Years later, I bought a copy of Red Hat 6 at a Costco. Windows 95/98 was big, I didn’t know how to pirate it, so I went back to Linux and it worked great on my “franken-puters” cobbled together from spare parts dumpster diving. Steep learning curve back then, though. Then I brought it to my workplace, went from UNIX admin to Linux admin, and soon I preferred it to Windows. Been my daily driver for decades, now.

    Am I an evangel? A little, but I find that “right tool for right job” is a better approach. Linux is great for everything, BUT a comprehensive system like MS Office AND Active Directory simply does not exist in FOSS space yet; everything is cobbled together and a kludge still trying to catch up.

    Obsessed? Kinda. I just assembled some ansible scripts to roll my own distro. Why? To see if I could.


  • I worked in a job with build scripts. Developers would list what they wanted in a drop-down menu on a website, with very few “fill in the blanks.” This would create a template, which was sanity-checked.

    One of the “fill in the blanks” was “home directory of user, if not default /home/username.” Some people filled it in, some didn’t. A lot of “users” might be apps with /home being “/opt/appname” “/var/www/html” or something. We checked to make sure that directory existed, if not, create, and set permissions. Easy peasy, all automated. Ran this lots of times.

    Then one day, the script failed. Borked the whole box. Sometimes the VM was corrupt, so delete VM and try again. Usually worked. But this time, the build kept failing. The box went down. Wasn’t even bootable. This happened several times with this one build. So we mounted the borked drive under a new VM and checked out the logs. Just like the dessert stage of Willy Wonka chewing gum, it always failed at the last stage: making /home directories.

    It would create them, then halt that it could not find bash. We looked for bash on the bad drive, and it was the usual /bin/bash shortcut to /usr/bin/bash and we were truly puzzled. I did a chroot to the drive and NOTHING worked. It just hung. That was the first clue.

    The second was looking through the build script (in bash, which we didn’t write) and checking the steps. Looked it the logs. Always died at creating some user named sapadm, the user for the HANA database. Eventually, I checked the configure file, and noticed it was the only user with the odd home directory “/usr/sap.” Then it hit me: the permissions.

    The script, thinking it was a home directory, did a chmod - R 755 for all directories and chmod - R 644 for all files! That meant, while creating home, it made everything under /usr not executable anymore! Holy shit, no wonder nothing worked! So we commented out that user in the config, ran the build again, and we were good! We created the sapadm by hand, and then later fixed the bug in the script.

    SANITIZE YOUR DATA. Or you might turn Violet Beauregarde into a blueberry.


  • In high school, we had a science fiction club. I was vice president in my senior year. A year after I graduated, I was hanging out with some fellow graduates and one of them said, “How come you hated Christine so much?”

    “Who?”

    “Christine Smith. The blonde girl?”

    “The blond girl who wore all those surfer shirts?”

    “Yeah. Whats so bad about her?”

    “Nothing. She was always so quiet. I barely remember her.”

    “Yeah, well she practically threw herself at you, and you treated her like she didn’t exist.”

    “She did?”

    “Yeah. We even tried to make it easy. We set her up at parties to talk to you, and you just acted like she wasn’t even there. You were so rude.”

    “I literally had no idea. I totally would have dated her.”

    “Yeah, well, too late. She got so depressed after you graduated, that she ended up dropping out of everything and tried to kill herself. Shes been hospitalized and her parents moved away to be with her. Like, couldn’t you gave even said hi? Just because you made vice president of the club didn’t mean you were better than her or something.”

    I literally had no idea.