Switch to pymobiledevice3

[zner0L]

It would seem that https://github.com/doronz88/pymobiledevice3/ would solve a lot of our iOS related problems. It already bundles usbmuxd and lockdownd for us in a PyPI package, which is amazing and would make #71 unnecessary, since we already have a way to manage python dependencies in our projects. It also supports everything we currently use libimobiledevice for and more:

• Install and list apps on the device
• Show device information
• Port forwarding (iOS: Use iproxy instead of having the user specify an IP address for SSH #43)
• Collecting the network traffic with pcapd and attributing is to specific processes
• Install configuration profiles (iOS: Support for managing certificate authorities #44)
• Mount developer image and use developer functions, e.g. setting a honey location or starting apps

[baltpeter]

Looks cool. Let's give it a go.

[zner0L]

I was so sure that switching to pymobiledevice3 was the best option, but now I found https://github.com/danielpaulus/go-ios, which implements the ability to install profiles in supervised mode, implements many features of pymobiledevice3 and is already distributes via npm (though the postinstall script seems to be a little broken). Sadly, it also lacks some features I liked in pymobiledevice3, notably creating and restoring backups, which I was planning to use for non-jailbreak installation of supervision and device reset. So, I see two options going forward:

• Implement session escalation for supervised devices in pymobiledevice3 (they seem to release quite often) and use that
• Fix the postinstall in go-ios and use that, ignoring backup and restore

[zner0L]

Well, I also just tested both on Windows and both still need the Apple Device Drivers, of course, but work without any other configuration.

[zner0L]

I lean towards implementing session escalation in pymobiledevice3, because I like the API more and the ability to easily extend it to add new functions. And with autopy we have a way to deliver python dependencies relibaly anyway and don’t need our depenendecies to be on npm. What do you think, @baltpeter?

[baltpeter]

I've only taken a quick glance at them, so I don't know which one is "better". I don't really have a preference regarding a Go vs. Python dependency. The Go one has the disadvantage that it doesn't currently ship arm binaries.