file uri scheme

Network securityHTTPS, TLSIn 2015, TLS is a minimum baselineMany servers default to TLSv1.0, from 1999Newest version is TLSv1.2TLSv1.2 is not enough. Compromise of a server key lets you decrypt all TLS traffic that was encrypted in the past.With forward secrecy, a server key compromise will only let you read future traffic. Past traffic will not be able to be decrypted.By default, apps linked against iOS 9 and OS X 10.11 cannot make unprotected HTTP connections.TLS connections will need to comply with best practices- Exceptions can be declared on a case-by-case basis in your app's Info.plist file.System Integrity ProtectionDefense in DepthSecurity is about layersOne layer failing shouldn't defeat all securityRely on multiple layers of protectionDelay the attackerReduce your attack surfaceSeque into talking about Vauban and star fortresses. History lesson FTW.OS X's star fortress security model:Outermost line - Developer ID and GatekeeperSecond layer - Sandbox - attacker only gets access to the data which the

HiI'm validating my receipts against the appstore, following the Apple's guide The receipt is retrieved from the bundle using the following code:NSURL *receiptURL = [[NSBundle mainBundle] appStoreReceiptURL];NSData *receipt = [NSData dataWithContentsOfURL:receiptURL];NSString *base64Receipt = [receipt base64EncodedStringWithOptions:0];The encoded receipt is a signed binary file, as described in the documentation. However, in some weird cases the receipt is not the expected binary file but an NSDictionary with the form{ pod = 50; purchase-info = ewo...; signature = Apdx...; signing-status = 0;}When I try to validate those receipts against the appstore, the result is always 21002 (The data in the receipt-data property was malformed or missing). Any ideas in why the receipt retrieved from the bundle is in the wrong format?Regards

I've updated the app for watchOS 2 using the built in suggestion with Xcode 7 when you first build it. I've changed all the necessary code so there's no errors or warnings but I can't seem to run either the containing app or the watch app in the simulator; they never launch but they do copy over to the simulators.Is there a new scheme I should be using? I'm using the previous scheme for the main watch app which now automatically lets you choose between running the iPhone 6 simulator with either the 38mm or 42mm watch simulator.

Over the course of Swift's existence I've had to take advantage of a number of workarounds (i.e., hacks) to compile a Swift framework that utilizes non-modular system code, e.g., CommonCrypto, sqlite3, etc.These solutions have included:Renaming the umbrella header to be something different than the module name in order to exploit a bug that let frameworks compile with bridging headers, wherein the non-modular import happened: #import <CommonCrypto/CommonCrypto.h>Building a dummy, optional framework with a custom module map specifying the absolute path to an SDK header (relative SDK paths don't work): module CommonCrypto [system] [extern_c] { header /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/usr/include/CommonCrypto/CommonCrypto.h export * }Specifying a custom module map with an additional header specifying the absolute path to an SDK header: framework module MyCrypto { umbrella header MyCrypto.h header /Applications/Xcode.app/Contents/Developer/Pla

I am working on an App where after the user completes the Revert to Saved… time machine like dialog the system sends a bunch of error messages to the XCode console:Jun 9 20:16:52 BDM-2.local Mandelbrot[36183] <Error>: CGContextClipToRects: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.Jun 9 20:16:52 BDM-2.local Mandelbrot[36183] <Error>: CGContextSetFillColorWithColor: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update....None of these graphics commands are part of my code. The document w