Understanding Mac OS X Kernel
An anonymous reader writes "Kernelthread.com has published a flash presentation overview of the Mac OS X kernel. Its title is 'A Tour of the Mac OS X Kernel' and it also covers Tiger features. Maybe interesting to note is that the slides are from a talk given to the NSA. Well, there is a nice security architecture diagram towards the end of the presentation."
A flash presentation that didn't turn my p4 into a 386!
Apparently not:
http://en.wikipedia.org/wiki/AES#Security
Does it give away the kernel's secret recipe?
I'm willing to bet it's in Flash because he did the presentation in Keynote. While the SWF export in Keynote isn't great, at least it preserves transitions, fonts, and other formatting options and doesn't look like shit (like the HTML export of another presentation software).
Plus, it takes one step to export. I haven't seen anything that will do that with CSS.
Per Square Mile, a blog about density
So HFS+ can only support file sizes up to 8 exabytes. What a worthless filesystem.
nil
FS and swap encryption is used to encrypt user's home directories. This is the "File Vault" functionality of OS X. Tiger adds the ability to optionally encrypt the users swap space also (only on file vaulted home folders) to secure the users memory space as well. A file vaulted home folder becomes a sparse disk image file (a disk image that can grow in size as it's written too) that uses the users account password to open. If the user losses their account password then the admin can use the master file vault (set separately) to restore the users home directory. That scenario only really applies for multi-user systems.
I am not sure what bit of AES is used though. I would guess 128 bit at least.
Embedded C++ is upwards compatible subset of ANSI Standard C++. So if you have written very simple C++, for example when coming from C and making your first C++ program, you probably "used" EC++. It is just C++ without namespaces, templates, exceptions, RTTI (Runtime Type Identification), STL (Standard Template Library), and some other stuff that might make executable noticeably bigger and cause unwanted memory consumption.
Like this: http://www.codepoetry.net/archives/2003/10/26/case sensitive_hfs_for_the_masses.php