I’ve recently read the Dana ODell article on Medium.com regarding and discussing an idea on how Apple could help “good samaritans” whose, finding our lost iOS device – and particularly an iPhone, to contact the device’s owner with ease. Thing that now it’s not so easy to do if the phone is locked by a code, or anyway request the finder to dig into our address book, or contact list, or recent phone calls…
I’ve liked it so much that I’ve used the Apple contact form to fill-in a request citing this article directly.
OK, I know… this post Clear in the iCloud is almost one year old today, but still… It’s interesting and insightful, at least for me, to grasp all the aspect of the design and engineering of a (successfull) app: Clear.
Which by the way in these hours has gone free (as in beer) maintaining the promise declared by Realmac Software in their Making Things Right letter to their customers!
Clear uses a custom system built on top of iCloud File Storage and it works in a similar fashion to Operational Transformation. The post proceeds to cover the reasons for choosing iCloud, then explores iCCD and subsequently builds a synchronisation system from the ground up.
Yesterday, Apple pushed a rather spooky security update for iOS that suggested that something was horribly wrong with SSL/TLS in iOS but gave no details. Since the answer is at the top of the Hacker News thread, I guess the cat’s out of the bag already and we’re into the misinformation-quashing stage now.
I coded up a very quick test site at https://www.imperialviolet.org:1266. Note the port number (which is the CVE number), the normal site is running on port 443 and that is expected to work. On port 1266 the server is sending the same certificates but signing with a completely different key. If you can load an HTTPS site on port 1266 then you have this bug. Adam Langley – Apple’s SSL/TLS bug