(Part 2) Reddit mentions: The best macintosh operating system books

Yeah, i was looking at this one. Looks like it is even cheaper as a Kindle book. http://smile.amazon.com/Apple-Pro-Training-Essentials-Troubleshooting-ebook/dp/B00HJUBRN8/ref=sr_1_5?s=digital-text&ie=UTF8&qid=1412167705&sr=1-5&keywords=Mac+OS+mavericks

Thanks!

Michael Wohl wrote a great book for FCP - he goes over concepts like dialog editing, action editing, etc. While the book is built around FCP and has media that works with FCP - the media and concepts will work with any editorial tool.

Craft Editing

You can always buy a jailbreak. Exploit brokers like zerodium pay out 1.5 million dollars for remote jailbreak 0-days.

Side note: *OS Internals Volume III by Jonathan Levin is a good source for people interested in learning about previous techniques used in jailbreaks

A great resource is the official certification textbook, http://www.amazon.com/Apple-Pro-Training-Essentials-Troubleshooting/dp/0321963555/

That's what all of my students study out of when preparing for the ACSP exam, and it goes into more detail than you'd expect about troubleshooting, the startup processes, LaunchAgents/Daemons, etc.

Places like this is where I got "photorealistic" from. I originally read the word in this book back in the day. Maybe I could have used a better word.

I've heard from a few people that this book is great for those with a basic programming foundation who want to get into iOS development.

John Siracusa writes reviews of new major OS X releases for Ars Technica. These reviews are more than a dozen pages long (to the point that the most recent one is also available as a Kindle ebook), so he has to start writing them well in advance of the actual release, using the developer Golden Master seed.

howardgrigg is implying that he will now have to start all over, since he may have found bugs that are now fixed, or successfully used features that now have bugs. (In reality, he'll probably just go through and retest everything—or at least every bug—he mentioned individually.)

• Learning Python
  
• Programming Python
  
• first read Learning Python, then Programming Python... best combination. Covers everything from basics, OOP, to threading, networking, GUI programming...etc.

"Core Animation for Mac OS X and the iPhone"
https://www.amazon.com/Core-Animation-Mac-iPhone-Programmers/dp/1934356107

Actually principles the same as for iOS. Also recommend try this: https://www.paintcodeapp.com (expensive but have trial version). Also check tutorials for Paintcode, IMHO 1-month enough to understand principles of custom control creation.

I've always enjoyed Matt Neuburg's books.


http://www.amazon.com/Programming-iOS-7-Matt-Neuburg/dp/1449372341

Oh yeah, we wouldn't want that.

I've learned the most from macProVideo and these two books:

• Logic Pro X 10.1: Apple Pro Training Series: Professional Music Production
  
• Apple Pro Training Series: Logic Pro X Advanced Audio Production: Composing and Producing Professional Audio
  

Sure, here you go:

<http://www.amazon.com/OS-10-9-Mavericks-Technica-Review-ebook/dp/B00G3J8NPQ/ref=sr_1_1?ie=UTF8&qid=1383035965>

I learned a fair amount from Swift for Beginners. It went off into the weeds occasionally with some advanced stuff, but it gave me enough of a base so that I can now work my way through Apple's Language Guide, and am absorbing that stuff without getting overwhelmed.

http://www.techradar.com/us/news/computing/apple/the-linux-users-guide-to-mac-os-x-624449

Most thorough book on OS X: http://www.amazon.com/gp/product/0321963555/ref=pd_lpo_sbs_dp_ss_3?pf_rd_p=1535523722&pf_rd_s=lpo-top-stripe-1&pf_rd_t=201&pf_rd_i=1449332315&pf_rd_m=ATVPDKIKX0DER&pf_rd_r=1QDDYGBHMR9CG5DR1RDZ

Do you already know a programming language? If so then O'Reilly's pocket reference for an overview then either the Apple docs or BNR for depth.

iOS has numerous amounts of security mechanisms in place

1. KASLR (Kernel Address Space Layout Randomization) - this randomizes the location of the kernel in the device. It makes it extremely hard to guess where the kernel is located therefore making it harder for exploits to target the kernel
   
   
2. App Sandboxing - Each app downloaded is 'sandboxed' which basically means its in its own cell. Apps cannot communicate/look at files without explicit permission from Apple, and even if Apple did give explicit permission (permission to camera roll, etc) it wouldnt be a big security risk either way
   
   
3. KPP (Kernel Patch Protection) This is the by far one of the hardest security mitigations implemented by Apple - Basically once the phone boots, KPP is then kicked up into Exception Level 3 and it acts as a guard for some major parts of the Kernel. Basically if something is modified at the kernel level, the phone will panic and reboot
   
   
4. AMFI (Apple Mobile File Integrity) This basically checks to make sure that the code written is verified and signed by Apple. We can use ROP to work around with this. Basically ROP is using Apple's own code to write an exploit.
   
   These are some of the basics and there are lots of good resources out there. I will link some of them below.
   
   https://xerub.github.io/ios/kpp/2017/04/13/tick-tock.html - KPP
   
   https://www.theiphonewiki.com/wiki/Main_Page - iPhone Wiki
   
   https://www.amazon.com/MacOS-iOS-Internals-III-Insecurity/dp/0991055535 - iOS internals
   
   http://newosxbook.com/index.php - iOS internals and code