this post was submitted on 11 Dec 2023
398 points (96.9% liked)
Technology
59593 readers
3396 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
You seem confident about "no benefit here". Are you sure about that or is that the flavor of the boot polish that you are tasting?
Also, "backdoor into iMessage", wtf?
Proprietary, closed source, third-party software that hasn’t been audited by a third party, that’s hooking into another proprietary protocol without the owner of said protocol’s approval.
Sounds to me like Apple fixed a security vulnerability they were exploiting to gain access to the platform. Honestly it reminds me of Microsoft and AOL with the AIM and MSN Messenger wars. I believe AIM used a buffer overflow on purpose for authentication, despite it being a serious security vulnerability.
Of course Apple doesn't want others to access the iMessage protocol. It's part of their walled garden. They can claim it's a secure protocol because they have full control over it. An application like Beeper gaining access undermines this.
Beeper doesn't access some sort of global repository of messages, but we've no idea what Beeper does with the conversations that are had via their clients. With iMessages you trust Apple, feel about that how you will, with Beeper you trust whoever is in charge of that.
Beeper is never going to last anyway. If they manage to regain access to iMessages, Apple will just update the protocol to reject them again. With Apple implementing RCS there's not really any point in applying legal pressure on Apple to open up their platform either.
Just hopping on to concur:
"Apple could release their own iMessage client for Android if this were really about trusting beeper, but it's not. It's about using peer pressure with blue bubbles to sell more iPhones."
It's just that simple (and offensive).
Claiming their protocol is "security by obscurity" would not be the win for them you think it is.
All of this has already played out before, some ~20 years ago. Microsoft wanted MSN Messenger to be compatible with AOL's Instant Messenger, so they reverse-engineered the protocol, only for AOL to update it, breaking the compatibility. It went back and forth until Microsoft revealed that AOL was using a buffer overrun exploit in their client to do remote code injection in order to authenticate the client.
Apple will never allow Beeper to exist; there's no point investing any time or money into it as whenever they manage to sneak back in, Apple will boot them back out. Perhaps some sort of legislation will fall in place forcing Apple's platform open, but given that they're implementing RCS I somehow doubt it.
Further, we know nothing about Beeper as a platform. It can/could speak with iMessages, but then what? How do we know it's secure? Because the owner of the product says so?
If the idea is to get secure and encrypted messaging between an iOS and an Android user, why not go for something like Signal that's open source?
Here is an alternative Piped link(s):
All of this has already played out before, some ~20 years ago.
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.