this post was submitted on 09 Apr 2026
84 points (82.8% liked)

Technology

83696 readers
1312 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
84
We Found a Ticking Time Bomb in macOS TCP Networking - It Detonates After Exactly 49 Days - Photon Blog (photon.codes)
submitted 3 days ago* (last edited 3 days ago) by warbosstodd@piefed.social to c/technology@lemmy.world
31 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] homes@piefed.world 5 points 3 days ago* (last edited 3 days ago)

Yeah, macOS, like most UNIX/BSD and Linux systems (even NT systems), use BSD‘s rather ancient TCP/IP stack. And, like most systems, have found their own unique ways around whatever bugs once existed (or still exist) in that stack.

This case uses iMessage as an example, and it would be kind of foolish not to think that between the TCP/IP stack and Apple‘s internal messaging system there isn’t some kind of time reset handler before it gets handed off to iMessage.