iOS 9 iCloud Drive support

[picklepete]

iOS 9 iCloud Drive support

[haoxi911]

@horrorho Thank you, as far as I know, Apple only provides SDK for iCloud Photo Library in iOS, and it is very easy to use. I also believe they have same feature implemented on macOS, and they just didn't want to make it public.

By the way, if you intends to use iCloud API in server end, maybe you should take a look at their CloudKit JS component, and wrap it into Node.js (I guess).

[guybask]

didn't work for me either.
Did apple stopped supporting their own API ??
Did they changed it ?
What has changed ?

[coddingtonbear]

It's difficult to say, @guybask; keep in mind that this project is entirely written by people not working for Apple -- we're all working on this in our spare time -- so it's really on the community as a whole to figure out what happened by reading Apple's release notes or experimenting.

[torarnv]

The iCloud Drive web interface seems to be using a combination of the drivews and docws services, not the ubiquity web service that pyicloud implements. Doesn't seem like drivews and docws would be too hard to implement if anyone wants to have a go at it.

[schuon]

do you have a pointer for documentation where to start?

[torarnv]

Open up the inspector in Chrome and use the network tab with the XHR filter to see what happens when mucking about on the iCloud.com website.

[rodrimc]

Is there anyone working on this?

[torarnv]

Nope, feel free to grab it!

On 17. mar. 2016, at 22.09, Rodrigo Costa [email protected] wrote:

Is there anyone working on this?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

[prateek1108]

Hi,
I am also facing the same issue on ios 9 icloud backup backups of ios 8 and below are listed. i also tried iloot same issue is there in that.

[horrorho]

Hi there. No idea if anyone is interested but I do have iCloud/ iPhotos iOS 9 working on an experimental/ hacked version of InflatableDonkey. It's based on CloudKit which was reversed for the project a while back.

The core CloudKit protobufs we reversed last year are out of date but work well. I do have newer protobufs available. The code base is also bit obtuse as it was based off my initial interpretation of Apple binaries, but I've tidied up the most troublesome areas.

Let me know if you need any information here or just open tickets on InflatableDonkey.

[haoxi911]

Just want to confirm, is this library (Python) or InflatableDonkey (Java) are both built by capturing and analyzing the traffics of icloud.com, so the HTTP endpoints used in the libraries are not officially supported Apple, and could be changed by Apple without letting us know?

I am building an application to access iCloud Photo Library on Mac (actually I didn't see an approach in CloudKit on Mac), and the application is commercial and will be delivered to consumers, I am not sure if I should translate this library to Swift or Objective-C and use as a solution.

Any suggestions?

[horrorho]

@haoxi911 InflatableDonkey was built on reversing Apple binaries more so than http traffic analysis. I often joke it was largely an exercise in reversing engineering binaries.

InflatableDonkey understands a subset of iCloud APIs but on a very low level. There are hacked versions of InflatableDonkey that do download iCloud photos/ documents without issue using it's iCloud code.

I'm not aware the iCloud API is in the public domain. Apple does like to fiddle with it so you'll need to anticipate beta changes and keep on top of them. As an example Apple introduced light protection zones whilst I was halfway through InflatableDonkey that required further reversing of binaries to elucidate the new mechanics. It's also crypto heavy so be prepared for that.

I had started working on an unofficial iCloud API in Java but I just don't have the time right now. As a compromise I had started writing a book detailing the iCloud API but I'm struggling to even find time for that.

[horrorho]

@haoxi911 Thank you. I've only examined CloudKit JS briefly. As far as I can see the it has security protocols/ boundaries in place that would prevent you from creating an application such as InflatableDonkey or what I suspect an updated pyicloud would like to be. Though obviously I could be mistaken and would be happy to be corrected

It's probably fair to state that InflatableDonkey exhibits unintended behaviour. It allows you to do something that Apple do not officially condone or particularly want. As it stands it can access public containers for any application it chooses without the use of server-to-server keys. Modified variants have also been able to exploit loopholes such as the now patched 'deleted iPhotos' issue that Elcomsoft also reported on.

Also just be clear. I'm not a developer, I don't own any iOS devices and I have no experience with Xcode. I don't claim any expertise in this field.