this post was submitted on 31 Oct 2026
165 points (98.8% liked)

Selfhosted

63507 readers
526 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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
[–] hirihit640@sh.itjust.works 8 points 3 days ago (1 children)

From what I read about regarding the PHP vulnerabilities, the RCE was extremely difficult to pull off. I'd guess it's the same here, at least until some non-AI companies weigh in, since these AI companies tend to distort the reporting and severities quite a bit.

[–] probable_possum@leminal.space 4 points 3 days ago* (last edited 3 days ago) (1 children)

Thank you.

Difficult as in unlikely that the exploit works or difficult to write an exploit? The latter doesn't help me much. :)

Regarding the php2shell issue: a lot of admins took their services down until it was patched. It's more a decision based on a guess - big number bad, evil acronym scary - than actually understanding what the exploit does. One can either believe it or not.

And that's the thing about the recent exploit (multipath TCP): I can't evaluate myself, whether the issue is likely an exploitable RCE. That is one factor missing in risk assessment: is the outcome potentially fatal? Yes, rce and priv escalation. Is it likely? I can't tell.

I'm sorry. I don't mean to doubt your expertise. I simply don't know you. It is the same with hackernews, the author repeats what he's or she's told. (Good overview article though. Thanks again for it.) RN It's: Someone from the internet said don't panic. A link to a statement from the Ubuntu package maintainer or distribution would make me feel at ease. I still couldn't make sure for myself - a lack of time and competence in the field - but I would trust it.

[–] Ooops@feddit.org 3 points 3 days ago* (last edited 3 days ago) (1 children)

Difficult as in unlikely that the exploit works or difficult to write an exploit?

Difficult as in it's a race condition that can theoretically be exploited when you get the timing right. But timing, if it's not on a well-known isolated system right before you in some lab, depends on a million details, some –once we are talking about real-life examples– outside your control.

[–] probable_possum@leminal.space 4 points 3 days ago

Yes. Anthropic wrote: it took them like an hour to get it right on their lab system. That's different than the wild wild internet.