161
Linux Kernel TCP Flaw With 9.8 CVSS Score Affects Ubuntu, Red Hat and Other Distributions (thehackernews.com)
submitted 1 week ago by to c/selfhosted@lemmy.world
24 comments fedilink hide all child comments
 

Every Go application since 1.24 will activate MPTCP on their sockets by default.

And I've read that this includes Syncthing, which is why I'm posting this here

you are viewing a single comment's thread
view the rest of the comments
[–] 41 points 1 week ago (5 children)

Could everyone stop blowing holes in things please, spent all yesterday rebuilding internet facing servers.

On the plus side, everything will be up to date. So there's that

Also with both this kernel and the php thing, Debian had a fix way before the big corporations. Even Amazon

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 4 points 1 week ago (3 children)

    rebuilding internet facing servers

    Because of one vulnerability?

    Jebus. Response at one site was a 10-minute thing and then letting cron do the work.

    Where the hell is your D-R? I worry you've made some very non-optimal decisions in the past and are taking on way too much work now.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 6 points 1 week ago (2 children)

    It took longer than planned as we are in the process of getting everything sorted for quick rebuilds, most of the time was waiting for GitHub to not poo it's self.

    If we had everything in ansible it would be 5 minutes

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 week ago* (1 child)

    If we had everything in ansible it would be 5 minutes

    Ansible at the day-job takes about 45 min to do a patch. As someone who's used a fair number of alternatives, maybe consider anything else on the planet?

    But, seriously. The response to this particular sploit wasn't really "config management"-y. It was a simple process that cron generally handled anyway, and network segregation and firewalling allowed us to prioritize easily. My worry is that there are some core architectural decisions you may need to revisit in the post-mortem on this, because there may be some fundamental changes required to get sensible wins in the future.

    (If you're on containers, I weep for your validation challenges; also, get bazel)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 11 points 1 week ago

    that's the point. you're supposed to be exhausted enough so that you just relent and let AI take over your duties.

    second objective is to showcase your incompetence to leadership so they are scared enough to replace you with AI.

    this is the plan.

  • permalink
  • fedilink
  • source
  • parent