5 ms·
Reverse Engineering the Apple Multipeer Connectivity Framework (2022)
- xpe 3y ago> I’ve heard way too many negative stories about [Apple's] disclosure program and in general how they mistreat researchers. Links?
- deedree 3y agoI did some lazy searching and it seems it's a well known fact. I don't think the author has to back it up in this case. Infosec researchers say Apple’s bug-bounty program needs work[0] [0] https://arstechnica.com/information-technology/2021/09/infosec-researchers-say-apples-bug-bounty-program-needs-work/ https://arstechnica.com/information-technology/2021/09/infos...
- _lvbh 3y agoWait times over 8 months and they refused to give credit (but gave $). Personal experience so I can’t say for others. They pay well though. My first year of college has been completely covered by them so no complaints.
- xpe 3y agoFrom a comment in the article: > This gives me chills, the shared clipboard also uses this protocol, right? This means that everything we copy goes through the network via Bluetooth without encryption and can be captured by any Bluetooth sniffer? The shared clipboard uses this protocol?... on what basis is this claim plausible?
- NathanWilliams 3y agoI thought it was clear it ran through iCloud: https://support.apple.com/en-au/HT209460 https://support.apple.com/en-au/HT209460 It only works between devices signed in with the same Apple ID
- jdsnape 3y agoThe encryption keys are shared via the iCloud keychain, but I think the actual sharing happens over a protocol called Companion Link.
- unglaublich 3y ago> on what basis is this claim plausible? The article shows the author holds some grudges against Apple. Those grudges probably influence their judgement.
- lapcat 3y agoThe comment in question was not written by the article author.
- dalbin 3y agoFrom Apple Platform Security Guide [0] : > The individual messages are encrypted much like messages in iMessage are. After the devices are paired, each device generates a symmetric 256-bit AES key that gets stored in the device’s keychain. This key can encrypt and authenticate the BLE advertisements that communicate the device’s current activity to other iCloud-paired devices using AES256 in GCM mode, with replay protection measures. [1]: https://support.apple.com/en-gb/guide/security/secf78dbe639/web https://support.apple.com/en-gb/guide/security/secf78dbe639/...
- lapcat 3y ago> From a comment in the article: To be clear, it's a comment on the article, in the public comments section appended to the article. The comment was not made by the article author.
- xpe 3y agoAgreed. My comment was worded poorly. Thank you for clarifying.
- fisherjeff 3y ago“Moreover, while sending crafted packets and attempting all sorts of things, I’ve discovered several vulnerabilities in the Apple custom made parsers. I will not discuss them here (exception made for the session spoofing) but at the same time I’m not interested in reporting them to Apple…” Erm, hope they’re not super serious I guess?
- ithkuil 3y agoTaken out of context it looks a bit weird, but it does explain the motivation: "I’ve heard way too many negative stories about their disclosure program and in general how they mistreat researchers."
- Avamander 3y agoYeah. Plenty of such stories, I had to reproduce a security issue across four macOS versions before it was finally fixed. Such a waste of time.
- isodev 3y ago[flagged]
- iforgotpassword 3y agoSo the question is whether those bugs are in the framework part provided by Apple, or the application specific code handing the individual messages.
- madeofpalk 3y agoIt's two lines in an otherwise pretty indepth technical article. Hardly a tantrum.
- Gorbzel 3y agoWhat he’s basically saying here is “I’d rather let my personal opinion prevail than responsibly disclose and get some vulnerabilities fixed.” Even if, at their worst, Apple is as petty as he’s “heard” (given the FUD surrounding quite a lot of engineer’s), the proper response is responding with less pettiness, not more. It’s reflective of the author’s character no matter how he expressed the tantrum.
- mannyv 3y ago"custom (and as typical of Apple, undocumented) TCP protocol" Pretty much all custom protocols are undocumented. Not sure why he feels the need to shit on Apple. And any custom protocol parser will be riddled with errors, because they always expect values to be in range.
- tjoff 3y agoBecause when apple does it you can assume it only works on apple devices, such a bore. How people can get excited about vendor lock-in beyond me.
- iforgotpassword 3y ago> And any custom protocol parser will be riddled with errors, because they always expect values to be in range. I hope you're not working on any products I rely on.
- joshspankit 3y agoApple has one of the most damaging two-faced approaches where on the public side they say they are all about openness and power users and security but on the private side they are intentional and severe about keeping that public image at the expense of users. I agree that there’s no responsibility on Apple to document this specific protocol but it’s important to see it in context.
- brookst 3y ago> they say they are all about openness and power users and security They do mention security a lot, but “all about openness and power users”? That’s not my impression. They famously eschew the “make everything a setting” philosophy. The whole Apple thing is simplicity at the expense of configurability and control. Do you see them otherwise?
- joshspankit 3y ago> but “all about openness and power users”? That’s not my impression. ...! I feel like a frog that’s just been shown the bubbles forming on the bottom of the pot. Granted I’ve been pretty “meh” on Apple the last few years but I’ve still watched the keynotes and kept up with their growth. I didn’t even notice that Apple cleaned developers and pro users from their brand! (pro users as defined by those that are always stretching the limits of the tech, learning, and finding new optimal ways to do things). I just finished re-watched the uncut WWDC keynote and when developers are mentioned they are now almost entirely talked about in 3rd person while Apple is talking directly to upper management. The most hands-on-tech thing they did was talk for a couple seconds about the WebKit features. My impression of Apple is shockingly outdated in their favour. The product pages for both Mac Studio and the Mac Pro (both “Pro” products) either talk specs without highlighting what can be done with them or they talk about media creation. The target demographic here is creative professionals and not technical ones, power users, or developers. They have served creative professionals for a long time for sure, but they also served power users and technology professionals because they recognized that it was them working with the creative professionals (and sometimes working on their own) to build products with huge markets. I thought that this was still an underlying corporate value at Apple but I see now that they’ve just conveniently dropped it without even a whisper. I guess their new core demographic is content creators and movie studios? Apologies if this rambles. I had to get it out. I’m still processing this.
- dosatlas 3y ago> My informed guess was multicast DNS as I’ve seen this protocol being (ab)used a lot from Apple (Bonjour for instance) I understand it's in fashion to kick Apple (and not without reason) but mDNS and DNS-SD is their protocol. They made it and they market it combined with link-local addressing, etc as Bonjour. To me writing like this is naff and makes the author seem needlessly salty.