Slashdot Mirror

← Back to Stories (view on slashdot.org)

Encrypting a User's Home Directory Under Mac OS X

Posted by CmdrTaco on from the now-ya-see-it-now-ya-don't dept.

jnetsurfer writes "A friend of mine challenged me to see if I could place a user's home directory on a device image (DMG) under Mac OS X. Well, I decided to post my solution to the problem on the web and here, in case anyone is interested. This can be useful if you want to encrypt a user's home directory, or if you wanted to limit a user's home directory to a certain size."

21 of 87 comments (clear)

  1. Cool article--one concern/question: by vegetablespork · · Score: 3, Interesting
    Is the handling of encrypted DMG files part of the open source Darwin, or is it possible that there is a crippling of or backdoor into this encryption that Apple was forced to insert at the behest of some three letter government or four letter lobbying agency, a la Lotus' having fixed part of the encryption key, effectively reducing key length in international versions?

    --

    Call (206) 338-5780 COLLECT for information about a genuine BA, BS, MA, MS, MBA, or Ph.D.

    1. Re:Cool article--one concern/question: by xmath · · Score: 4, Informative

      The DiskImages framework and associated utilities (hdid, hdiutil) are not part of Darwin.

      And sadly the encryption "plugin" is embedded inside the framework rather than being external. So if you'd want to check for backdoors, you'd need to disassmble the whole DiskImages framework (in /System/Library/PrivateFrameworks) and plow through that.

      However, since it does seem use a plugin interface, even internally, it's probably not too hard to locate just the encryption-related parts.

    2. Re:Cool article--one concern/question: by plsuh · · Score: 4, Informative

      The underlying AES-128 encryption is part of the Darwin distro. Look in the Darwin sources under:

      src/Security/AppleCSP/AES/

      This still doesn't really address the whole question -- if there's some back door somewhere higher up the stack in the disk mounting code, you won't find it here, but it's part of the solution. Validate the AES-128 code, then treat the encrypted disk image as a black box (using a simple password, without loss of generality) and see if you can decrypt the image by hand or using a util that you write yourself.

      OK, I work for Apple so you really can't fully trust me on this, but I certainly don't know of any intentional back doors in this code.

      --Paul
      psuh at apple dot com
      Curriculum Developer
      Technical Training and Certification
      Apple Computer

  2. Encrypted files systems... by tvadakia · · Score: 3, Interesting

    This brings up a point. A friend of mine has been researching a way for an entire operating system (a widely used one like MacOS or Microsoft Windows) to use, exploit, and be fully functional on top of a completely encrypted file system. Or, for a file system such as NTFS or HFS+ to reside as a sub-file system, being contained within an encrypted file system, with which if you enter the system with the correct password (or biometrics or card key or combination) you'll enter the system, and the OS which resides on the system doesn't even notcie the underlying encrypted-FS and only sees the contained NTFS/HFS+/etc... Is this possible? If so, how?

    --
    Unique.
    1. Re:Encrypted files systems... by hdurdle · · Score: 4, Informative

      PGP Disk.

      The freeware version is here. I've used it before, and it works like a charm. You create a PGPDisk file on a normal volume - this contains an encrypted disk. You can then "mount" the drive after providing the correct password. I've used it in the past on NT4 and on Win2K to great effect.

    2. Re:Encrypted files systems... by hdurdle · · Score: 3, Interesting

      While I'm thinking about this... you could even run aVMWare virtual machine using a disk image on a PGPDisk encrypted volume. That way you can run any kind of Windows or Linux on a machine where the OS will have no clue that it's entire underlying file system is encrypted.

    3. Re:Encrypted files systems... by xmath · · Score: 3, Informative

      Note that on MacOS X, using disk images like the author of the article described is *exactly* like using PGPdisk, except PGPdisk is cross-platform and perhaps more trustworthy since its source is available for auditing.

      Using OSX' diskimages however is free-as-in-beer, and probably a bit more flexible. Can you even mount a PGPdisk from the commandline on OSX ?

    4. Re:Encrypted files systems... by battjt · · Score: 3, Informative

      It's been done on shrink wrapped secure laptops running Linux/VMWare/W2K. The user only sees W2K, but everything is running in a vm on secure Linux.

      I doubt that it is worth the trouble though. You generally only need to encrypt data, not executables.

      Joe

      --
      Joe Batt Solid Design
  3. Re:limit a user's home directory to a certain size by snowtigger · · Score: 5, Informative

    Here we go, I found these unix commands in OSX 10.1.5:

    man quota
    man quotaon
    man quotacheck

    I have been using different encrypted file systems on Linux, mostly using the twofish algorithm. Basically, I think there are two major purposes of crypted file systems for the average geek:

    1) You've got some REALLY secret information which you'd like to protect: use an encrypted file.
    2) You would like to protect the information in case someone steals your computer.

    In my opinion, crypting the whole system doesn't really make sence unless you're afraid of someone coming to take your computer away from you: To use the computer, you have to unlock these filesystems anyway and an intruder will be able to read your files at that time ...

    Also, encrypted filesystems heavily slows down the system, since every read/write to disk needs some CPU. I remember getting pretty poor transfer rates, which is the reason I don't use it anymore.

  4. So how strong is AES-128? by ubiquitin · · Score: 3, Insightful

    According to this helpful how-to, you use the Disk Utility to make an image using AES-128 encryption and then you store your home directory on that image.

    The NIST has a white paper on AES which announces that the Rijndael method was the official AES algorithm and that Rijndael is designed with some flexibility in terms of block and key sizes.

    Apparently 128 bit AES allows for a possible 3.4 x 10^38 possible keys which (correct me if I'm wrong here) puts it somewhere between DES and triple-DES. (?)

    Can any Mac users comment on the limitations that are imposed on your choice of a passphrase?

    Basically, I'd like to know how strong a method is this. Is it keep your little sister from reading your diary encryption, or more along the lines of if the Feds busted you they couldn't crack open your data with any computers due out in ten years type of encryption.

    --
    http://tinyurl.com/4ny52
    1. Re:So how strong is AES-128? by cbiffle · · Score: 3, Informative

      128-bit AES allows for 128-bit keys, so yes, in decimal, 3.4e38-somethingorother (2^128). Yes, this is a greater range than DES (2^56). It's also greater than 3DES using two keys (one for the first and third stage, one for the second, so 2^112). Proper 3DES implementations use three independent keys for an effective keyspace of 2^168.

      However, the keyspace of an algorithm is only one of its strengths. It's only relevant if brute force is the fastest way to crack the cipher, which is very rarely the case. In the case of DES, it was refined by the oft-maligned NSA to resist differential cryptanalysis, leaving it resistant against all but brute-force until linear cryptanalysis was 'discovered' in the mid-90s. (To those who still believe the NSA weakened DES, go read your Schneier.)

      AES-128 is a new algorithm, but feels good. Brute-forcing a 128-bit keyspace would take several centuries, even taking into account Moore's law, so the difference between it and 3DES's 168 bits isn't relevant. Moreover, there are known exploits against 3DES (even if they aren't terribly helpful), whereas massive scrutiny by cryptanalysis worldwide (while Rijndael was becoming AES) has turned up nothing so far. This doesn't mean there won't be exploits, but it means that the chances that Shamir or one of the other hotshot cryptanalysts is going to bring out a paper tomorrow that invalidates all your work are very small.

      So: AES-128 will keep your sister from reading your diary. Unless you believe the NSA has some sort of amazing quantum computing that's forty years beyond consumer tech (which I really, really don't), AES-128 is also likely to keep your files safe from the gimmies for several decades.

      Although why the NSA would be interested in, say, my homedir, is beyond me -- the most likely person trying to crack my encryption is probably a jealous girlfriend. :-)

  5. Ditto... by TiMac · · Score: 4, Informative
    In the steps listed to change the home directory to the encrypted disk...a given step (#6) says to use "sudo cp -R /Users/USERNAME /Volumes/VOLUME-NAME/" to move the current home directory. But this will not properly copy resource fork files, so some files and programs would break...so most likely you would want to use

    sudo ditto -rsrcFork /Users/USERNAME /Volumes/VOLUME-NAME/

    instead, which maintains the Resource Fork information.

    --

    1. Re:Ditto... by TiMac · · Score: 5, Informative
      Actually,

      I just realized that because of a behavior of ditto, you'll want it to be:

      sudo ditto -rsrcFork /Users/USERNAME /Volumes/VOLUME-NAME/USERNAME

      Sorry for the little oversight :)

      --

  6. OK It's strong. by ubiquitin · · Score: 3, Informative

    I kept reading and found the answer to my own question: in the late 1990s, specialized "DES Cracker" machines were built that could recover a DES key after a few hours. By trying possible key values, the hardware could determine which key was used to encrypt a message.

    Assuming that one could build a machine that could recover a DES key in a second (i.e., try 255 keys per second), then it would take that machine approximately 149 thousand-billion (149 trillion) years to crack a 128-bit AES key. To put that into perspective, the universe is believed to be less than 20 billion years old.

    --
    http://tinyurl.com/4ny52
  7. Re:Linux by snowtigger · · Score: 3, Informative

    Here you go, this HOWTO is even more complete than the article referenced for Mac OS X.

    http://weigand.home.texas.net/efs.html

    Of course, there are Linux distributions that does it out of the box. I use Suse that does this just fine ...

  8. Re:Not fast by Pfhor · · Score: 5, Insightful

    Why would you be storing your mp3s on an encrypted disk?

    I would think personal financial documents and porn would be much more important. Of course mpeg playback would be hindered, which would be a problem.

  9. Think different -- a better way to do it by plsuh · · Score: 5, Informative
    This is actually something that is covered in the new Mac OS X Administration and Integration sysadmin technical training course from Apple that will be going live in January. As the author of that section of the course, let me give you a bare bones outline here.
    1. Log in as the user whose files you want to secure.
    2. Create an encrypted disk image using Disk Copy at the top level of the user's home directory. When it asks for the disk image password, be sure that the "remember password" option is checked -- this saves the disk image's password on the user's default keychain.
    3. Use ditto to copy over the following directories from the user's home folder onto the encrypted disk image:
      ~/Desktop
      ~/Documents
      ~/Library/Mail
      ~/Applicat ion Support/Addresses
      ~/.ssh
      These are the important ones; you can copy over other items as well, but definitely don't do the entire ~/Library folder, and don't do the ~/Library/Keychains or ~/Library/Preferences folders.
    4. Set the disk image to automount on login by dragging it into the Login Items preferences pane.
    5. Use mv to shift the directories aside (e.g. mv ~/Documents ~/Documents.save) and set up symlinks onto the disk image (e.g. ln -s /Volumes/Secure/Documents ~/Documents).
    6. Log out and log back in again. The disk image will be automounted at login, using the password stored on the default keychain which also unlocks on login. Everything should just work! :-D
    7. Now for the housekeeping: delete the .save directories you created earlier, and be sure to turn off automatic login in the Accounts preferences pane.
    Why do it this way instead of the way that Joshua Gitlin wrote up? First, you don't need admin access to a machine to make it work. You may not have admin access on a company machine, or as a sysadmin you may not want to give admin access to most of your users.
    Second, using Joshua's method, once the disk image is mounted it's open to anyone who has admin access on that machine, whether or not you are logged in at the console. By using an automounted image with the password stored on the keychain everything is secure until you actually log in, and everything is secured once you log out.
    Third, this way is a lot more convenient. If you make security too inconvenient, users will circumvent it. Instead of two logins, you only have to do one. Techincally unsophisticated users (secretaries, lawyers, vice-presidents, etc.) don't need to do anything different.

    <BLATANT PLUG>
    Go to Apple Training and sign up for a course or two. They're well worth the money and help me keep my job. :-D
    </BLATANT PLUG>

    --Paul
    psuh at apple dot com
    Curriculum Developer
    Techincal Training and Certification
    Apple Computer
    1. Re:Think different -- a better way to do it by tbmaddux · · Score: 3, Interesting

      Since you're putting the password in the keychain, and most user passwords are the same as their keychain passwords, doesn't this present a potential weak point? (I've often read not to put AES-128-encrypted .dmg passwords into the Keychain) How secure is the password database in MacOS X?

      --
      Can't you see that everyone is buying station wagons?
    2. Re:Think different -- a better way to do it by plsuh · · Score: 3, Insightful

      On Mac OS X, the password is stored as a standard Unix-style crypt hash with eight significant characters. It's no more or less secure than most other Unix-style systems that use this system -- this is reasonably secure if you use a solid password. Upper and lower case, numbers, punctuation, etc. I'd personally prefer that it take into account more significant characters, but "this will be covered in a later release". Using the OpenLDAP-based password server from Mac OS X Server gives you 255 significant characters via SASL, but this isn't usable in the case where you want encrypted disk images the most, on a laptop away from any network.

      A pretty good way to make a difficult to crack but easy to remember password is to string together two words with some punctuation in between. E.g., my old (now defunct, so don't bother trying it) Compuserve account password, "knife:other". On Mac OS X, this reduces to "knife:ot" which is easy to remember but hashes to something pretty difficult to crack by brute force.

      --Paul

      Curriculum Developer
      Technical Training and Certification
      Apple Computer

  10. Encrypted disk image access speed by plsuh · · Score: 5, Informative

    One more thing -- people have been commenting/asking about the speed of access. The algorithm for AES-128 on MOSX 10.2 has been heavily optimized. There is basically little or no additional overhead when using an encrypted disk image vs. an unencrypted disk image.

    --Paul

  11. Re:What I meant was... by alyandon · · Score: 3, Informative

    NTFS 5 (in 2000 and XP) supports transparent encryption of entire volumes which might be what you are looking for. I'm not sure if you can encrypt the entire boot partition or not as I'm not interested in that level of security. Unfortunately, if you encrypt data you lose the ability to use NTFS's transparent compression.