• 1 Post
  • 111 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle



  • Oh my god.

    sh -c "$(curl -fsSL https://raw.githubusercontent.com/knadh/listmonk/master/
    

    We absolutely need to stop this. Sure, I saw the disclaimer, but we need to end the normalization of running ANY black-box crap off the net. “curl|sh” needs to be laughed into exile for all our safety.

    The easiest thing needs to be the right thing – common security saying

    Then it’s

    vim
    

    As if that’s actually user-friendly or a positive experience instead of the worst thing to ever survive from the last century, crawling along on its rotting flesh and drooling on the pavement like some toxic residue from the vietnam war that it is.

    In what asylum do you have the people willing to suffer vi and who also need a curl|sh ? Are they lazy or just misled as noobs into thinking vi is the only editor out the–

    You guys, I just realized how vi masochists actually reproduce. It’s like zombies, guys, eating brains until the victim raises up another zombie.

    And that curl|sh – does it invite supply-chain exploits? Ohhh, you bet it does! Best black-box script ever! Use this as a test for your security people – if they gauge this as a threat from within another threat, they pass. But, honestly, had it not been for the horrible spelling, I wouldn’t have thought to check further. \shrug. Mineshafts and canaries I guess.














  • Biggest pain point was for our ops guy, who constantly had to stay behind to perform upgrades and maintenance,

    This is weird.

    Hosts selected for updates will be unavailable from 2100-2110 or so. Then they’re up.

    They’re done by at/cron if they’re selected.

    There’s no manual work if the monitoring system thinks they’re okay.

    Gitlab-ce on-prem. Although that may now suck since they’re being bought out; and we all know how that went for redhat.