Xe Iaso

https://xeiaso.net/blog

39 posts · 39 Votes · 3 Followers

Tech 87% · Gaming 8% · Life 5%

Subscribe via RSS

  1. "No way to prevent this" say users of only language where this regularly happens

    In the hours following the release of CVE-2026-45250 for the project FreeBSD, site reliability workers and systems administrators scrambled to desperately rebuild and patch all their systems to fix a kernel stack overflow when validating permissions of the setcred(2) system call, allowing arbitrary code execution in the context of the kernel. This is due to the affected components being written in C, the only programming language where these vulnerabilities regularly happen. "This was a…

    0 ▲
  2. "No way to prevent this" say users of only language where this regularly happens

    In the hours following the release of CVE-2026-45584 for the project Microsoft Windows, site reliability workers and systems administrators scrambled to desperately rebuild and patch all their systems to fix a memory safety vulnerability resulting in arbitrary code execution inside the virus scanner Windows Defender. This is due to the affected components being written in C++, the only programming language where these vulnerabilities regularly happen. "This was a terrible tragedy, but sometimes…

    0 ▲
  3. Amazonbot is finally respecting robots.txt

    I just got an email from Amazon saying they're finally going to respect robots.txt. Here's the verbatim email I got: We are writing to inform you that starting Monday, June 15, 2026, crawl preferences for Amazonbot will be managed solely through the industry-standard directives. This gives you direct, ongoing control over how Amazonbot accesses your site, rather than relying on manual requests. If you do not implement robots.txt directives by that date, Amazonbot will follow standard web…

    0 ▲
  4. I'm really frustrated that GitLab is doing layoffs

    GitLab announced layoffs today. They don't state how many people are affected, but honestly I find this really frustrating for several reasons: This is the one time where they could have won by doing relatively nothing. GitHub is having big outages on a daily cadence. All they have to do is market themselves as "we're the stable one" and maybe add tooling to run your existing GitHub Actions in GitLab to make the transition easier. They could have won so hard it's not even funny because GitLab…

    0 ▲
  5. Slowly going mad with power using Tekton

    I'm not feeling good about the future of GitHub https://red-squares.cian.lol/ I have a bunch of repos I'd like to migrate off of GitHub One small problem: all my CI flows assume I'm using GitHub Actions I mean this is reasonable, I've used GitHub Actions for most of my career All my GitHub Actions flows only really work on GitHub I've moved some of them off of GitHub in the past, but it requires some significant modification and hacking because my actions really rely on GitHub platform features…

    0 ▲
  6. Maybe you shouldn't install new software for a bit

    In the wake of copy.fail, there are more vulnerabilities that have been announced: Copy Fail 2: Electric Boogaloo Dirty Frag Right now would be one of the best times for a supply chain attack via NPM to hit hard. Outside of Linux kernel patches from your distro, I think it's probably a good idea to put a moratorium on installing new software for a week or so.

    0 ▲
  7. Claude Code won April Fools Day this year

    They gave people a heckin tamagochi, what's not to like?

    0 ▲
  8. Small note about AI 'GPUs'

    They are graphical processing units that can't process graphics.

    0 ▲
  9. Homelab downtime update: The fight for DNS supremacy

    Turns out everything DID NOT go offline somehow. Yay!

    0 ▲