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

  • 0 Posts
  • 19 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle










  • Punkie@lemmy.worldtomemes@lemmy.worldStupid meetings
    link
    fedilink
    arrow-up
    16
    ·
    edit-2
    2 months ago

    One of the things I have learned is that a lot of middle management don’t have tangible roles, so they make up for this by recognition, which is usually “presence.” So they have meetings to be seen, stay relevant, and look important. Like, how do you measure management as a product? It’s a social game, primarily. I’m not saying all or any large percentage of management is like this, but there are a LOT.

    “What do you say you DO here, exactly…?” And they start to sweat.

    Edit: Clarifying I know there ARE effective ways for an organization to do this, but that doesn’t mean they do or even know how :/


  • When I was in theater camp as a pre-teen, one of our actors was a very enthusiastic foot guy. I had heard of foot fetishes, but never understood them. But this guy was like an overexcited fan boy of feet. My curiosity triggered this guy into a huge brain dump, and one of the things he went on about about how feet were the “true expression of a person’s feelings.” Feet turned towards you? They like you. One foot pointed away? They don’t. He then showed me how girls’ feet would match their mood, so no matter what parts they were rehearsing, he could tell their underlying mood: anxiety, sadness, anger, happiness, etc… I have no idea if he was right, but that was my first exposure to another person’s fetish. I could only understand it abstractly, but I found it fascinating.






  • Basic setup for me is scripted on a new system. In regards to ssh, I make sure:

    • Root account is disabled, sudo only
    • ssh only by keys
    • sshd blocks all users but a few, via AllowUsers
    • All ‘default usernames’ are removed, like ec2-user or ubuntu for AWS ec2 systems
    • The default ssh port moved if ssh has to be exposed to the Internet. No, this doesn’t make it “more secure” but damn, it reduces the script denials in my system logs, fight me.
    • Services are only allowed connections by an allow list of IPs or subnets. Internal, when possible.

    My systems are not “unhackable” but not low-hanging fruit, either. I assume everything I have out there can be hacked by someone SUPER determined, and have a vector of protection to mitigate backwash in case they gain full access.



  • Worked a job where I had to be a Linux admin for a variety of VMs. To access them, I needed an VPN that only worked inside the company LAN, and blocked internet access. it was a 30 day trial license on day 700somthing, so it had a max 5 simultaneous connection limit. Access was from my heavily locked down laptop. Windows 7 with 5 minutes locking Screensaver. The ssh software was an unknown brand, “ssh.exe” which only allowed one connection at a time in a 80 x 24 console window with no ability to copy and paste. This went to a bastion host, an HPUx box on an old csh shell with no write access to your home directory due to a 1.4mb disk quota per user. Only one login per user, ten login max, and the bastion host was the only way to connect to the Linux VMs. Default 5 minute logout for inactivity. No ssh keys allowed. No scripting allowed, was like typing over 9600 baud.

    I quit that job. When asked why, I told them I was a Linux administrator and the job was not allowing me to administrate. I was told “a poor carpenter always blames his tools.” Yeah, fuck you.