this post was submitted on 06 Dec 2023
185 points (82.9% liked)
Technology
59235 readers
3184 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Doesn't iMessage require some sort of Apple-issued device id? A key, unique to a device, hard-coded in the SoC? (which is easy to block if over-used).
Which is why hackintoshes used to require crazy workarounds to get this working, even with Apple's own software, if I remember correctly (never tried myself, could be wrong).
How did they get around this? (did they?)
It does, the article actually mentions that. Yes, they did get around or reverse-engineer it. The article does not describe how, though I imagine it's doing the same sort of workaround that Hackintoshes have to do. Honestly, it's quite a feat.
Check out my reply
I posted some links that get into the details of how the tech works
This blog post does a fairly good job outlining the tech
You can also take a look at the pypush proof-of-concept code that this is based on
Thanks, the second link talks about this in the
"data.plist" and Mac serial numbers
section.