5 ms·
iOS 14 USB tethering broken on Linux: looking for docs and contact at Apple
- threeseed 6y agoMake sure you also file a Radar at: http://bugreporter.apple.com http://bugreporter.apple.com They do get triaged just not necessarily actioned depending on priorities etc.
- xvector 6y agoURL doesn’t work for me, but you can also just type “applefeedback://“ in Safari to create a ticket.
- dfabulich 6y agoThat's the wrong URL. The correct URL is https://feedbackassistant.apple.com/ https://feedbackassistant.apple.com/
- saagarjha 6y agoI suspect you meant https://bugreport.apple.com/ https://bugreport.apple.com/, which is also accessible via rdar:// on consumer iOS devices. Sadly, the redirect service that has been running their ever since it was replaced by Feedback Assistant seems to not be working at the moment :(
- dfabulich 6y agoThat's the wrong URL, too. Just use https://feedbackassistant.apple.com/ https://feedbackassistant.apple.com/
- saagarjha 6y agoIt’s not the wrong URL, it’s the old URL. Until recently it was just as effective as the URL you gave.
- cmeacham98 6y agoSSL_ERROR_UNSAFE_NEGOTIATION when connecting in firefox. https://www.ssllabs.com/ssltest/analyze.html?d=appleseed.apple.com https://www.ssllabs.com/ssltest/analyze.html?d=appleseed.app... > This server is vulnerable to the Zombie POODLE vulnerability. Grade set to F. > There is no support for secure renegotiation. > This server does not support Forward Secrecy with the reference browsers. Grade capped to B. > This server supports TLS 1.0 and TLS 1.1. Grade capped to B. What the fuck?
- cookiengineer 6y ago> POODLE vulnerability. Maybe the domain still uses the gotofail [1] prone implementation of Apple's SSL library? [1] https://nvd.nist.gov/vuln/detail/CVE-2014-1266 https://nvd.nist.gov/vuln/detail/CVE-2014-1266 Personal note: After that CVE was disclosed in 2014, I decided to ditch all Apple hardware forever. There is absolutely no security on any Apple device. The bug meant that there was not a single working SSL encryption from Apple's first OS up until (and including) OSX 10.9.2 and iOS 7.0.6 ... which kinda speaks volumes on Q&A or security audits.
- reanimus 6y agoWere all of the other OS X versions affected, too? The CVE only lists 10.9.x (so, 10.9 and 10.9.1)
- cookiengineer 6y agoYes, all previous OSX version up until 2014 were affected, too. The doubled `goto fail;` line was included since the first public revision of libsecurity_ssl, and the (c) of that file is 1999-2001,2005-2012 Apple Inc. [1] Nowadays, due to Apple never using any git or any other version control software for opensourced codes, I could trace it down to Mac OSX 10.4 which was released in 2005. [2] With 10.1, there's no libsecurity open sourced, I don't know why, but I'm pretty damn sure that at least 10.2 included the library back then. I don't have my old Powerbook G4 anymore, but I swear I could verify this bug on 10.2 (Jaguar) that was running on it at the time. Other versions of (maybe patched?) versions of libsecurity-ssl are located on the same server, with a global directory for everything so it's not actually versioned!? [3] At least the version of the file that has copyright 2000-2001 still has the same bug in it, so that is very likely the one that was used in the 10.1 public release [4] [1] https://opensource.apple.com/source/Security/Security-55471/libsecurity_ssl/lib/sslKeyExchange.c.auto.html https://opensource.apple.com/source/Security/Security-55471/... [2] https://opensource.apple.com/release/mac-os-x-104.html https://opensource.apple.com/release/mac-os-x-104.html [3] https://opensource.apple.com/source/libsecurity_ssl/ https://opensource.apple.com/source/libsecurity_ssl/ [4] https://opensource.apple.com/source/libsecurity_ssl/libsecurity_ssl-6/lib/sslKeyExchange.cpp.auto.html https://opensource.apple.com/source/libsecurity_ssl/libsecur...
- jojobas 6y agoDoes Linux even exist for Apple? They are where Microsoft was 15 years ago in that respect.
- tomjakubowski 6y agoMany if not most of their backend services run on Linux, which you can tell from their job postings.
- jojobas 6y agoI don't think their backend services tether with iphones. They wouldn't bother porting even such a fundamental tool as iTunes.
- threeseed 6y agoApple has been using Linux for at least a decade. Online Store and iTunes Store used to both run on it. These days I imagine everything does since they use Kubernetes for Siri, Maps etc.
- morpheuskafka 6y agoI'm surprised they don't use FreeBSD or some sort of in-house headless build of macOS, since their entire product line has been built around FreeBSD/POSIX base for macOS.
- hendry 6y agoI usually rely upon https://aur.archlinux.org/packages/libimobiledevice-git/ https://aur.archlinux.org/packages/libimobiledevice-git/ via https://wiki.archlinux.org/index.php/IOS https://wiki.archlinux.org/index.php/IOS I'm using the wifi hotspot since wired rarely works for me. $ sudo idevicepair pair No device found. with an iPhone running 14.0.1 over USB-C
- geofft 6y agoThe blog post links to this libimobiledevice bug report: https://github.com/libimobiledevice/libimobiledevice/issues/1038 https://github.com/libimobiledevice/libimobiledevice/issues/... (and the debugging has led them to the kernel driver side of things, not the libimobiledevice side of things)
- yread 6y agoIt gets broken every major release, sometimes even more often :(
- saagarjha 6y agoApple is probably not going to help for this, sadly. I am fairly sure the details of tethering are considered to be private API and when something like that breaks (having likely been created by reverse engineering originally) they just don’t care. That being said, perhaps you’ll get some support from some skills do reverse engineers to help update that code!
- teruakohatu 6y agoThere is space for "we will tell you how to works but no guarantees" between "private api" and "open spec".
- saagarjha 6y agoGenerally for Apple that space is fairly narrow.
- jeffbee 6y agoWhy do people use the USB tether? The WiFi hotspot always works perfectly, it's an open protocol etc.
- fenwick67 6y agoUSB tether is one less wireless signal to worry about. If you're tethering for a long time you're probably plugging your phone into your laptop anyway, to charge it.
- jeffbee 6y agoI always disliked wired tether and USB cellular modems because Linux thinks it knows about the link state and will close all your sockets if you briefly lost the carrier, whereas with WiFi tethering Linux is never aware of whether the phone has a carrier or not. The ergonomics are much nicer, imho. I admit I never tried the wired mode on iOS. Maybe it doesn't propagate the link state?
- geofft 6y agoThis is a silly solution, but can you solve this by creating a bridge device and putting the cellular modem (and nothing else) on the bridge? Then the link state of the bridge should remain up.
- Nextgrid 6y agoUnlike cellular modems, the iPhone acts as a router and the link state it propagates is the link state of a (virtual) interface connected to that router, independent of the state of the upstream cellular interface.
- Macha 6y agoI wonder why my experience is so different. I primarily use it while taking the train to my parents and for the second part of the journey the signal is bouncing between 2g/3g/no signal but I've not encountered this.
- kkaranth 6y ago
- ajharrison 6y agoBuy a Mac ya dummy.
- marcan_42 6y agoWow, this brings back memories. I hacked on this and other iPhone support on Linux back in the day, including on getting music sync support working, back when I myself used an iPhone. At the time I wrote usbmuxd, which implements the sync (not tethering) part of the protocol. I can now say that I had a bit of behind the scenes help from an Apple engineer; his tips helped work out some corner cases that would've been quite hard to track down otherwise. This friend sadly passed away a few years ago. Unfortunately, Apple has always been (publicly) hostile to third party support for their devices. For example, they insist on "signing" music databases with algorithms based on their FairPlay DRM implementation, to stop non-iTunes software from syncing music to them. I reverse engineered one variant of this (which was based on a white-box AES implementation and a lot of obfuscated junk) but they kept changing the algorithm. This went into libgpod and libimobiledevice.
- nanoscopic 6y agoIf you manage to get anyone from Apple to speak with you send them my way also. I am the author of IOS support for DeviceFarmer ( previously OpenSTF ). Part of that support involves getting video of the screen over the USB connection which uses the same undocumented pathways that libimobiledevice uses. I've been attempting to find someone at Apple to support the open source efforts for nearly a year to no avail. What I would like Apple to support is fetching the raw h264 stream in a documented fashion, rather than forcing one to use AVFoundation and get pre-processed frames/data. Only allowing decoded video makes it impossible to scale. ( having many devices connected to a single mac all streaming video ) It would also be awesome if they would open up and document all the protocols and operations that the lockdown protocol supports. I doubt that will ever happen though.
- dingaling 6y agoDoesn't there come a point where you just say "screw Apple" and leave their devices unsupported? They're deliberately opaque and obtuse. If people choose to buy their devices then they should accept the consequences of that choice.
- nanoscopic 6y agoI'm not an Apple user. The reason I've spent the last year and a half developing an open source solution to support Apple devices is because it is a challenge and is profitable. I view myself as a sort of technological mercenary. I go where my skills are needed. I don't own a personal mac laptop, nor do I use an iPhone. If Apple gave me a macbook pro and an iPhone I wouldn't use either. ( other than to develop software that requires those ) I do though believe in making required technical things easier for others. It is a good feeling making something possible with IOS devices that hasn't been done as open source previously. Creating and testing IOS apps isn't something that will cease to be just because hardcore developers dislike the closed Apple ecosystem. The people who fund Apple, in my opinion, aren't hardcore geeks. They are the normal folk in the world. My only request to Apple is to please listen to what the developers want and provide some of the information I need so that I can in turn improve the development experience for the developers that are already paying into their ecosystem. Sitting on your high horse saying "I don't like the way big companies function" doesn't pay the bills or convince anyone you are a good engineer who will stay professional regardless of your personal feelings.
- CSDude 6y agoI went to summer house to work and got my old Linux with me. For 10 days, I was out of internet bc wifi driver (obscure brand) was also broken. It was very frustrating, now I know why!
- villgax 6y agoVice versa Android USB tethering is broken on MacOS
- tlrobinson 6y agoBummer, I just picked up a nice little cheap GL.iNet travel router ("Mango" and "Slate" are popular models) that works (worked?) with USB tethering on iOS (presumably pre-iOS 14). I'm sure WiFi tethering will still work with it, but it's nice to remove one potentially flaky connection from the equation.
- mariuolo 6y agoHow about running Windows in a VM and utilising Wireshark to analyse the protocol?
- paulcarroty 6y agoHeh, I remember when tried to tether my iphone wifi connection to Linux desktop first time and didn't know it's not supported by design, LTE-only.