| 26 | | Running the ''Build'' command should do the job for you. You'll find all the parts of the application in the ''build'' directory. |
| | 25 | |
| | 26 | == Usage == |
| | 27 | |
| | 28 | Use 'tmVaultCntrl' to enable, disable or query the status of the agent. |
| | 29 | The option -h prints out the commands this utility understands. |
| | 30 | |
| | 31 | |
| | 32 | Note: |
| | 33 | Make sure the vault is activated before switching user home |
| | 34 | directories. |
| | 35 | |
| | 36 | |
| | 37 | 1. Create a user account (if not already done). |
| | 38 | This account doesn't need administrative privileges. |
| | 39 | |
| | 40 | 2. From the user account run 'createEncDisk' in a terminal window. |
| | 41 | This will create an encrypted sparse bundle owned by the user |
| | 42 | which will be automatically mounted as '<username-Private>'. |
| | 43 | |
| | 44 | 3. Switch to an administrative account without unmounting the users |
| | 45 | encrypted disk. This can be done in a terminal window using the |
| | 46 | 'login' command. |
| | 47 | |
| | 48 | 4. From the admin account run 'setupEncDisk'. This will copy the users home |
| | 49 | directory to the disk image and create the symbolic link. |
| | 50 | |
| | 51 | 5. Logout the user and login again. Now the new encrypted volume should |
| | 52 | be in use. |
| | 53 | |
| | 54 | |
| | 55 | Hint: It's best to do all this while being logged in as an administrator. |
| | 56 | The user may just login in a terminal window to create the disk. |
| | 57 | |
| | 58 | |
| | 59 | After you find everything is just fine you may delete the old user directory |
| | 60 | in '/Users' which was renamed to '/Users/_<username>' during step 4. For |
| | 61 | maximum privacy use secure delete. |
| | 62 | |
| | 63 | To maximize privacy go to the settings of the private disk (Command-I) |
| | 64 | and deselect "Ignore ownership of this volume". |
| | 65 | |
| | 66 | |
| | 67 | == If something goes wrong == |
| | 68 | |
| | 69 | The script doesn't delete the users home directory after installing the |
| | 70 | files into the encrypted disk. So to recover just log into an admin account |
| | 71 | and delete the symbolic link in '/Users' and rename the old users directory |
| | 72 | from '_<username>' to '<username>'. |
| | 73 | |
| | 74 | |
| | 75 | == Known problems == |
| | 76 | |
| | 77 | * Logging out as a user does not unmount the encrypted disk. Still the file permissions apply preventing others from tinkering with your files (if properly set...). Yes, this is kind of a security issue and may be rectified in a later release. |
| | 78 | * There is no compacting of your encrypted image yet. This means the size of your image file doesn't shrink even if you delete files in it. |
| | 79 | * You have to delete the old user directory by hand after creating the encrypted one. This is not a bug but done on purpose. |
| | 80 | |
