Any gotchas for encrypted disk images?

I am about to set up e-bills and e-statements at various banks and credit cards and wanted to check a couple of things before doing something that may end up being bad
The assumption I am going with, is I will create an encrypted disk image to store all the PDF's.
1. Is that the right thing to do? Or is there a better way to keep the data secure?
2. If I do so, what is the backup impact? Can I simply set up a task to copy and paste the entire disk image to my external drive?
3. If I want to open the disk image on another computer, can I? How will it authenticate the user/pass on a different computer?
4. I can backup an encrypted disk image to a FAT-formatted external drive?
5. And finally, I have read disclaimers that if I forget the password the data is lost irretrievably. But also, that the password is stored in keychain. So if the password is stored in keychain, the worst-case scenario can only happen if I forget the master password, right? I don't need to truly remember the password to the disk image necessarily, right?

baltwo wrote:
Your profile info indicates that you're running Tiger. If so, post to those forums. If you're running Leopard, update your profile info. What are you trying to protect and from who? Is your computer secure?
IIRC, encrypted disk image passwords are independent from Keychain Access. So if you forget it, then you're hosed. BTW, that's the major failing with encrypted anything. If you forget the password, you're hosed. If the disk image gets corrupted, it's useless with or without the password. Anything stored in an encrypted disk image needs to be backed up in an unencrypted state and stored in some kind of physical thing like a safe. Methinks your a bit paranoid. Disable auto-login, use high-level passwords (that you remember), don't enable the root user account or activate a master password, and you should be secured enough.
I updated the profile. I am running Leopard. So this is the correct forum.
What am I trying to protect? I thought I put it in the first line - statements from banks and credit cards.
From whom? From unwanted entities who may get access to my computer, in any way.
I didn't get the part about the safe. Can I or can I not back up an encrypted disk image to an external drive "as is"? What about possibly opening it up on another computer? And how about putting it on a FAT-formatted disk? I repeat my original questions, but for a reason - they seem to have not been answered.
I do not have auto-login, and I remember my strong login password. I don't have my root account enabled. Under this scenario you think my data is going to be secure? What about if someone were to get control of my computer? Forgive me on this one, I am a switcher so there is a general paranoia about such things which I would like to clarify before reorganizing my life.

Similar Messages

Lost password for encrypted disk image

i created a encrypted disk image to store some personal files and now i can not remember my password and its not in my key chain is there a way to reset the password or at least recover the files.

If you could access the files on an encrypted disk image without knowing the password, there wouldn't be much point in encrypting it.
Do you remember anything at all about the password? Was it a name, or a dictionary word? If so, there might be hope of cracking it before the Earth passes away. You'd need the help of a consultant to do that.

Even though I have LCD font smoothing disabled, Mountain Lion still uses it in PDF views, Safari's location bar, Mail's message view, and the dialogs for mounting encrypted disk images.

Even though I have LCD font smoothing disabled, Mountain Lion still uses it in PDF views, Safari’s location bar, Mail’s message view, and the dialogs for mounting encrypted disk images. Is there any solution to this problem? Also diabled the Smoothing in the SystemPrefs and also via Terminal. Font smoothing is still there. Very annoying, especially in PDF attachments in Apple Mail.

Try feeding Safari a user-defined CSS file with font-smoothing tweaks (including none). The filename and its filesystem location are arbitrary. Use your favorite coding editor.
Safari > Preferences > Advanced > Style Sheet:
Here is an example with all elements uncommented. Pick the one that works best for your Safari viewing and comment out the others:
Preview. Try Preview > Preferences > PDF > Smooth text and line art (uncheck)

Can't paste password for new encrypted disk image.

Howdy all!
I have been trying to create an encrypted disk image with the Disk Utility, but I'm having trouble with putting in the password.
Using the password assistant, it only fills one of the two password fields, and I cannot copy/paste the password to the other field. If I generate a password elsewhere I cannot paste it into either box as well.
If I switch applications from Disk Utility and come back to the password dialog the menubar says I am still in whatever application I was last (in this case it says Firefox at the very left) and the Edit menu is completely grayed out.
Any idea how to get a non-typeable password into this dialog?
Thanks for your help.
Mike

You can paste it in if you use hdiutil to create or mount the disk image (In Terminal.app). That's the
only way to go if you use a "bullet proof monster" password like I do.
To create an encrypted, sparse disk image, open a Terminal window and cd to the directory in which
you want to create the image file. For example:
cd ~/Desktop
Then type the command:
hdiutil create -size thesize -encryption -type SPARSE -fs HFS+ thename
live command example:
hdiutil create -size 1g -encryption -type SPARSE -fs HFS+ myimage
(this will create a 1gigabyte sparse image with the hfs format with the name "myimage.sparseimage"
#note: I love sparseimages and sparsebundles because they mount so quickly#
Above, the size is the maximum size that the volume will ever be able to contain, for example,
660m for 660 megabytes or 1g for one gigabyte. Note that if you want the image file to remain
below a certain size (such as the size of a CD) you must allow for approximately 10% overhead.
Also above, thename is the name of the image file you want to create, not the volume name.
The volume name will be "untitled". Rename as you would any other mounted volume (after it is
mounted).
You will be asked for a password or phase to secure your file. In terminal you may copy and paste
or use command + V keyboard combo. It will mount normally after that.
I don't use the "Remember password (add to Keychain)" function because my passphrase will be
visible in the Keychain to anyone with physical access to your computer.
Instead I use Terminal to open my new image.
Open terminal.app, simply type:
hdiutil attach /path/to/imagefile
example:
hdiutil attach /Users/kj/Desktop/myimage.sparseimage
(remember, you can drag and drop the file path into the terminal from Finder)
Terminal will ask for your password, simply cut and paste from your favorite password program
(such as "1Password").
There is a manual page available; type man hdiutil in the Terminal.
Enjoy,
Kj

Various disk actions ask for the PW to my encrypted disk image, even though I'm not accessing this. Help

I have a small portion of hy hard drive set aside as an encrypted disk image. Since installing OSX Lion, various actions that dont require access to that disk image (printing to PDF, opening Aperture) ask for the password, and wont do anything til I provide that password. Has anyone else run into this, or more importantly, found a solution?
Thanks
Ted

See Here for Troubleshooting
Free Disc Space
http://www.thexlab.com/faqs/freeingspace.html
See Here for Resolving Startup Issues
http://support.apple.com/kb/ts1417

Unable to create an encrypted disk image in Lion

disk utility gives the error Unable to create "Volume.dmg." (error - 60008) when creating an encrypted disk image. I am using the following steps:
    1.    Open disk utility
    2.    Select the disk (internal or external) to create the image on
    3.    Select File>New>Blank Disk Image…
    4.    Save As: 'Volume'
    5.    Name: Volume
    6.    Size: 50GB
    7.    Format: Mac OS Extended (Journaled)
    8.    Encryption: 128-bit AES encryption
    9.    Image Format: read/write disk image
    10.    Click the Create button
    11.    Password dialog appears
    12.    When I enter a password the dialog closes after entering only a few characters i.e. before I've finished typing, and the following error message displays:
Unable to create "Volume.dmg." (error - 60008)
I have previously, successfully, created encrypted disk images in Snow Leopard, and I don't know why I can't in Lion
Does anyone have any ideas?

Thanks for this Thomas.
I've tried naming the image differently, but still received the error, I did however try different permutations for the password.
The error seems to happen if I use a purely numerical password string and occurs on input of the 10th numerical character, if I start with numerical character but use an alpha before the 9th number I can continue and create a password, and I can create a password if I start with an alpha and switch to numerals after the first alpha character, purely alphabetical passwords are fine too.
It seems that Lion doesn't like purely numerical passwords greater than 9 characters, whereas Snow Leopard wasn't so fussy. Seems it's a bit of a bug.
Thanks for your help

Creating an Encrypted Disk Image on an External (USB) Drive

I have an external 600 GB drive (2x 300 GB SATA 3.5" disks in a Thecus N2050 RAID0 external enclosure connected to iMac by USB2) onto which I would like to backup a large amount of data (500 GB).
I store this external drive away from my home (in the office) and since I cannot guarantee physically locking away the drive I would like to logically lock the drive by placing all the backup data into an encrypted disk image created on that volume.
I have tried creating an encrypted disk image on my USB volume in Disk Utility (Apple's instructions here) but I experience a number of issues not documented in the Apple article:
1) I am not presented with a drop-down option for the size of the disk image.
2) When I go ahead and try to creat the image I am told that the creation was impossible "file or folder does not exist".
Is it possible to create disk images on USB volumes (I cannot create such a large disk image on my iMac HDD as I do not have sufficient space).
thanks in advance
Raf

I realised that in Disk Utility you must not have any of your mounted drives highlighted in the left hand pane.

Corrupted files within encrypted disk images

Greetings Apple Hivemind:
I've run across a repeatable problem when using encrypted disk images from Disk Utility. Essentially, I'll create an image using settings like are shown below:
The disk image is then used for storing data. In my case, this is usually data for Adobe Lightroom.
At first, this worked very well, and I housed the disk images on my household NAS, connecting via samba (smb) to it on my Mac. Over time, however, something odd started happening: Files on those encrypted images began getting corrupted whenever I tried writing new data to them.
My first incident was where Lightroom informed me that the catalog it was trying to open was corrupted. I tried to create a new one on the same encrypted volume, and it too was instantly flagged as corrupted. I opened the individual image files on the volume with no problem, so I wasn't thinking that the volume was the culprit. That is, until I tried dragging new image files to it manually. The new files were immediately either completely unreadable, or a mish-mash of the content of random OTHER files on the volume!
The result was that all old data seemed intact, but I could no longer write new data to the volumes without major data corruption issues. I thought that this was isolated to one volume in particular, but it soon started happening on ALL of my encrypted volumes eventually. Including those which were not, and never had been, housed on my NAS, but were on my local hard drives.
I've since "evacuated" all my data from these images, since the ones created by Disk Utility appear to be useless, and am seeking an alternative.
Is this something that anyone else has encountered when using encrypted disk images? It seems like this is something I should really open a support ticket for, but I can't say I've ever tried it, so I don't know how successful it would be to do so.

bbonn wrote:
I should add that I've tried using the "Repair" and "Verify" functions of Disk Utility on the volumes, and despite the obvious issues that exist in them, the utility doesn't find (or fix) any inconsistencies.
Are you repairing/verifying the actual disk images, or just the partition they're on? If the partition, it won't look inside them.
Drag one to Disk Utility's sidebar, select it, then use Verify or Repair. Note: the usual messages may not appear on the DU window. Click the Log icon in the toolbar or select Window > Show Log from the menubar to see them.

Encrypted Disk Image creation slow?

I just got a new MBP with Leopard. I have created a number of encrypted disk images in the past using Tiger and a MBP and have not had any trouble. This weekend I tried a few times to create a 50 gig encrypted disk image (128 AES) on an external drive and after going through the process of setting it up and waiting for it to be created, (and watching the progress bar as it was being created), after about 45 minutes NO progress was showing on the progress bar. I ended up having to cancel the creation a few times because I thought something was going wrong. I’m not sure if there is a problem creating the disk image, or leopard is slow, or what.
Does anyone know how long, on average, it would take to create an encrypted disk image of this size using leopard? I just want to know if there is a problem doing this on my MBP. Thanks for the help.

A regular 50 GB disk image takes 50GB of space, no matter if it is full of files or empty.
A 50 GB sparse disk image only takes up the amount of space equivalent to that of its enclosed files. So if the 50GB sparse image only has 1 GB of files inside, the image won't be much bigger than 1GB.
A sparse bundle is similar to a sparse image, but instead of a single file it is a folder package with many, many enclosed files called bands. A new file added to the sparse bundle will tend to modify only a few bands. This makes incremental backups of a sparse bundle more efficient because only the changed bands need to be backed up again. Any change to a sparse or regular disk image will mean that the entire image will need to be backed up again.
If you regularly add/remove files to a disk image, and you intend to back up that disk image with Time Machine, a sparse bundle is definitely the way to go. The other types will fill up your TM volume very quickly.

Encrypted disk image creation very slow-

I just got a new MBP with Leopard. I have created a number of encrypted disk images in the past using Tiger and a MBP and have not had any trouble. This weekend I tried a few times to create a 50 gig encrypted disk image (128 AES) on an external drive and after going through the process of setting it up and waiting for it to be created, (and watching the progress bar as it was being created), after about 45 minutes NO progress was showing on the progress bar. I ended up having to cancel the creation a few times because I thought something was going wrong. I’m not sure if there is a problem creating the disk image, or leopard is slow, or what.
Does anyone know how long, on average, it would take to create an encrypted disk image of this size using leopard? I just want to know if there is a problem doing this on my MBP. Thanks for the help.

A regular 50 GB disk image takes 50GB of space, no matter if it is full of files or empty.
A 50 GB sparse disk image only takes up the amount of space equivalent to that of its enclosed files. So if the 50GB sparse image only has 1 GB of files inside, the image won't be much bigger than 1GB.
A sparse bundle is similar to a sparse image, but instead of a single file it is a folder package with many, many enclosed files called bands. A new file added to the sparse bundle will tend to modify only a few bands. This makes incremental backups of a sparse bundle more efficient because only the changed bands need to be backed up again. Any change to a sparse or regular disk image will mean that the entire image will need to be backed up again.
If you regularly add/remove files to a disk image, and you intend to back up that disk image with Time Machine, a sparse bundle is definitely the way to go. The other types will fill up your TM volume very quickly.

Password fails in encrypted disk image

I created a 300 mb encrypted disk image using 10.4.x, about 9 months ago, now I am running 10.5.2 and everytime I try to open the image and type in the password (the correct password I have been using for years) iI get an authentification error. I know Im using the correct password, any ideas what happened here. Could the image be corupted but still want me to authenticate?
I have not tried to open the file since Dec. 17th (via last modified date) I have check all the permissions on the eternal drive where the file is stored... also ran Techtool on the drive and found no errors... I am out of ideas...

I have encountered the same problem on two protected disk image files as well. Once in January and then again a few days ago.
I first thought that the first lockout was a fluke. Now after the second image lockout I'm very vary of opening another encrypted backup. I'm losing data. Even copies of the .dmg on different drives fail to authenticate. Searching for answers I found this thread.
Is it possible that a kernel panic / forced shutdown can corrupt an encrypted file? I wonder, but my encrypted home directory (FileVault sparsebundle) is fine.
Any insights would be appreciated.
This is my log:
Last login: Sun May 11 07:35:13 on ttys000
kevin:~ kevin$ hdiutil attach -debug /Volumes/kevin/busted.dmg calling DIHLDiskImageAttach with
agent: hdiutil
drive-options:
debug: true
image-options:
verbose: false
quiet: false
main-url: /Volumes/kevin/busted.dmg
2008-05-12 18:11:17.015 hdiutil[1745:1c03] using helper tool at "/System/Library/PrivateFrameworks/DiskImages.framework/Resources/diskimages-he lper".
2008-05-12 18:11:17.040 hdiutil[1745:1c03] connectToFramework
2008-05-12 18:11:17.141 hdiutil[1745:1c03] sendOperationToHelper: about to ask proxy to start operation
status proc called: initialize
2008-05-12 18:11:17.173 diskimages-helper[1747:1603] _imageOptions: {
"enable-keychain" = 1;
2008-05-12 18:11:17.176 diskimages-helper[1747:1603] _driveOptions: {
autodiskmount = 1;
"unmount-timeout" = 0;
2008-05-12 18:11:17.178 diskimages-helper[1747:1603] DIHelperAttach: initializing framework
DILoadDriver: checking for disk image driver...DILoadDriver: DI_kextExists() returned 0x00000000 (0)...DIIsInitialized: returning NO2008-05-12 18:11:17.188 diskimages-helper[1747:1603] -checkForPreviouslyAttachedImage: entry
2008-05-12 18:11:17.189 diskimages-helper[1747:1603]
file://localhost/Volumes/kevin/busted.dmg - (null) ((null), (null)). perm=0
DIIsInitialized: returning YESDIBackingStoreNewWithCFURL: entry with
file://localhost/Volumes/kevin/busted.dmg
skip-permissions-check: true
DIBackingStoreInstantiatorProbe: entry
file://localhost/Volumes/kevin/busted.dmg
skip-permissions-check: true
DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
CBSDBackingStore::newProbe score 100 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 1 CBundleBackingStore
CBundleBackingStore::newProbe score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 2 CRAMBackingStore
CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
CRAMBackingStore::probe: score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 3 CCarbonBackingStore
CCarbonBackingStore::newProbe: setting initial rval to +100
CCarbonBackingStore::newProbe: has resource fork, +100
CCarbonBackingStore::newProbe score 200 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 4 CDevBackingStore
CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Volumes/kevin/busted.dmg).CDevBackingStore::newProbe score -1000 for
DIBackingStoreInstantiatorProbe: probing interface 5 CCURLBackingStore
CCURLBackingStore::probe: scheme is
file
CCURLBackingStore::probe: not recognized URL scheme.
CCURLBackingStore::probe: score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 6 CVectoredBackingStore
CVectoredBackingStore::newProbe not "vectored" scheme.
CVectoredBackingStore::newProbe score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreNewWithCFURL: CCarbonBackingStore
DIBackingStoreNewWithCFURL: instantiator returned 0
DIBackingStoreNewWithCFURL: returning 0x00000000
2008-05-12 18:11:17.190 diskimages-helper[1747:1603] -checkForPreviouslyAttachedImage: resolving file://localhost/Volumes/kevin/busted.dmg returned 0
2008-05-12 18:11:17.191 diskimages-helper[1747:1603] -checkForPreviouslyAttachedImage: imageUID (
"d234881039:i8914"
) shadowUID (null)
*** testing:
0: d234881039:i9111
(null)
(null)
*** testing:
0: d234881039:i9111
(null)
(null)
*** testing:
0: d234881039:i9111
(null)
(null)
2008-05-12 18:11:17.194 diskimages-helper[1747:1603] DIHelperAttach: resolving disk image
DIIsInitialized: returning YESDIIsInitialized: returning YESDIBackingStoreNewWithCFURL: entry with
file://localhost/Volumes/kevin/busted.dmg
enable-keychain: true
image-path: /Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: entry
file://localhost/Volumes/kevin/busted.dmg
enable-keychain: true
image-path: /Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
CBSDBackingStore::newProbe score 100 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 1 CBundleBackingStore
CBundleBackingStore::newProbe score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 2 CRAMBackingStore
CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
CRAMBackingStore::probe: score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 3 CCarbonBackingStore
CCarbonBackingStore::newProbe: setting initial rval to +100
CCarbonBackingStore::newProbe: has resource fork, +100
CCarbonBackingStore::newProbe score 200 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 4 CDevBackingStore
CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Volumes/kevin/busted.dmg).CDevBackingStore::newProbe score -1000 for
DIBackingStoreInstantiatorProbe: probing interface 5 CCURLBackingStore
CCURLBackingStore::probe: scheme is
file
CCURLBackingStore::probe: not recognized URL scheme.
CCURLBackingStore::probe: score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 6 CVectoredBackingStore
CVectoredBackingStore::newProbe not "vectored" scheme.
CVectoredBackingStore::newProbe score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreNewWithCFURL: CCarbonBackingStore
opening /Volumes/kevin/busted.dmg setPermission 1723
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
closing /Volumes/kevin/busted.dmg setPermission 1731
DIBackingStoreNewWithCFURL: instantiator returned 0
DIBackingStoreNewWithCFURL: returning 0x00000000
DIResolveURLToBackingStore: processing level 1 encodings.
DIFileEncodingNewWithBackingStore: entry for encoding level 1
DIFileEncodingInstantiatorProbe: entry for level 1
enable-keychain: true
image-path: /Volumes/kevin/busted.dmg
DIFileEncodingInstantiatorProbe: probing level 1 interface 0 CMacBinaryEncoding
CBSDBackingStore::openDataFork: about to open /Volumes/kevin/busted.dmg
opening /Volumes/kevin/busted.dmg openDataFork 1904
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
closing 3 /Volumes/kevin/busted.dmg closeDataFork 1984
00000000: 656e 6372 6364 7361 0000 0002 0000 0010 | encrcdsa........ |
00000010: 0000 0005 8000 0001 0000 0100 0000 005b | ...............[ |
00000020: 0000 00a0 548a 2877 86c1 4f17 877b cf66 | ....T.(w..O..{.f |
00000030: beea 6066 0000 1000 0000 0002 780e 1734 | ..`f........x..4 |
00000040: 0000 0000 0001 e000 0000 0001 0000 0001 | ................ |
00000050: 0000 0000 0000 0060 0000 0000 0000 0268 | .......`.......h |
00000060: 0000 0067 0000 0000 0000 03e8 0000 0014 | ...g............ |
00000070: d369 cd83 75e8 bb7c 72e5 020d fdd3 68a9 | .i..u..|r.....h. |
diskimages-helper: fileNameLength $0000006E
diskimages-helper: resourceForkLength $60000000
diskimages-helper: dataForkLength $00000000
diskimages-helper: commentLength $00006700
diskimages-helper: MacBinary III signature (0x00000000)
diskimages-helper: header CRC $0000FDD3
diskimages-helper: minimum decoder version $0000000D
diskimages-helper: encoder version $00000002
no MacBinary III signature - checking for MacBinary I or IIDIFileEncodingInstantiatorProbe: probing level 1 interface 1 CAppleSingleEncoding
CBSDBackingStore::openDataFork: about to open /Volumes/kevin/busted.dmg
opening /Volumes/kevin/busted.dmg openDataFork 1904
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
00000000: 7263 6e65 6173 6463 0000 0002 0000 0010 | rcneasdc........ |
00000010: 0000 0005 8000 0001 0000 0100 0000 005b | ...............[ |
00000020: 0000 00a0 548a .... .... .... .... .... | ....T........... |
closing 3 /Volumes/kevin/busted.dmg closeDataFork 1984
CAppleSingleEncoding::isAppleSingleFile loadAppleSingleHeader failed with error 22
DIFileEncodingInstantiatorProbe: probing level 1 interface 2 CEncryptedEncoding
CBSDBackingStore::openDataFork: about to open /Volumes/kevin/busted.dmg
opening /Volumes/kevin/busted.dmg openDataFork 1904
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CEncryptedEncoding::copyHeaderInformation: inBackingStore->openDataFork returned 0
CEncryptedEncoding::copyHeaderInformation: inBackingStore->getDataForkLength (stub header) returned 0
CEncryptedEncoding::copyHeaderInformation: backingStore data fork length is 0x0000000278100000 (10604249088)
CEncryptedEncoding::copyHeaderInformation: reading V1 header from offset 0x00000002780FFB04 (10604247812)
CEncryptedEncoding::copyHeaderInformation: inBackingStore->readDataFork (stub header) returned 0
CEncryptedEncoding::copyHeaderInformation: not recognized as v1 header
CEncryptedEncoding::copyHeaderInformation: reading V2 header from offset 0x0000000000000000 (0)
CEncryptedEncoding::copyHeaderInformation: inBackingStore->readDataFork (stub header) returned 0
CEncryptedEncoding::copyHeaderInformation: reading auth-entry count from offset 0x0000000000000048 (72)
CEncryptedEncoding::copyHeaderInformation: inBackingStore->readDataFork (auth entry count) returned 0
CEncryptedEncoding::copyHeaderInformation: reading auth table from offset 0x0000000000000048 (72)
CEncryptedEncoding::copyHeaderInformation: inBackingStore->readDataFork (auth entry count) returned 0
closing 3 /Volumes/kevin/busted.dmg closeDataFork 1984
max-key-count: 1
blocksize: 4096
uuid: 548A2877-86C1-4F17-877B-CF66BEEA6066
version: 2
passphrase-count: 1
private-key-count: 0
CBSDBackingStore::openDataFork: about to open /Volumes/kevin/busted.dmg
opening /Volumes/kevin/busted.dmg openDataFork 1904
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
closing 3 /Volumes/kevin/busted.dmg closeDataFork 1984
CBSDBackingStore::openDataFork: about to open /Volumes/kevin/busted.dmg
opening /Volumes/kevin/busted.dmg openDataFork 1904
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
closing 3 /Volumes/kevin/busted.dmg closeDataFork 1984
diskimages-helper: DiskImages secure mode enabled
CEncryptedEncoding:unclockCANTHROW: trying to unlock with normal keychain
UNLOCK: cannot find passphrase in keychain search list.
UNLOCK: SessionGetInfo returned 0
UNLOCK: sessionHasGraphicAccess
UNLOCK: sessionHasTTY
UNLOCK: sessionWasInitialized
UNLOCK: using TTY to prompt for passphrase
Enter password to access "busted.dmg":
unlockCoreFromTTY: passphrase is wrong
DIFileEncodingNewWithBackingStore: returning 0x00000050
DIResolveURLToBackingStore: level 1 encoding match failed. 80.
DIResolveURLToDiskImage: resolving backing store/file encoding failed. 80.
status proc called: attach
error code: 80
status proc called: cleanup
2008-05-12 18:11:41.081 diskimages-helper[1747:1603] DIHelperAttach performOperation: returning 80
2008-05-12 18:11:41.082 diskimages-helper[1747:1603] -decrementBackgroundThreadCount: _backgroundThreadCount is now 0.
2008-05-12 18:11:41.082 diskimages-helper[1747:10b] DIHelper reportresults: reporting {
payload = {
"result-code" = 80;
2008-05-12 18:11:41.083 hdiutil[1745:1c03] reportResultsToFramework: proxy has finished operation
2008-05-12 18:11:41.084 hdiutil[1745:1c03] reportResultsToFramework: results are: {
payload = {
"result-code" = 80;
2008-05-12 18:11:41.084 hdiutil[1745:1c03] reportResultsToFramework: _threadResultsError is 80
2008-05-12 18:11:41.085 hdiutil[1745:1c03] reportResultsToFramework: disconnecting from helper.
2008-05-12 18:11:41.186 hdiutil[1745:1c03] disconnectFromHelper: removing observers
2008-05-12 18:11:41.187 hdiutil[1745:1c03] disconnectFromHelper: terminating proxy
2008-05-12 18:11:41.189 diskimages-helper[1747:10b] DIHelper: terminateHelper: entry.
2008-05-12 18:11:41.190 hdiutil[1745:1c03] disconnectFromHelper: terminated proxy
2008-05-12 18:11:41.290 diskimages-helper[1747:10b] -DIHelperAgentMaster terminateUIAgentConnection.
DIHLDiskImageAttach() returned 80
2008-05-12 18:11:41.293 diskimages-helper[1747:10b] DIHelper dealloc.
2008-05-12 18:11:41.294 diskimages-helper[1747:10b] -DIHelperAgentMaster terminateUIAgentConnection.
hdiutil: attach failed - Authentication error
kevin:~ kevin$

Nested items in docked folder inaccessible on mounted encrypted disk image

When I click on a folder in the dock, then select a nested folder and try to open it, I get the error message:
"The application cannot be launched. -35"
The folders in question reside on an encrypted disk image (which is mounted). If I remove the folder from the dock and then put it in the dock again, this fixes the problem until the disk image is unmounted, and then mounted again.
Are there any solutions? Thanks.
iMac G5 10.5.7

I finally discovered a quick and easy workaround for this problem.
Using Automator and Cocktail's "built in" Automator actions, I created a script with 2 actions. The first clears the user's dock caches (using Cocktail). The second action is a shell script that relaunches the dock. The script is simply "/usr/bin/killall Dock" (case sensitive, without the quotes).
I saved the Automator script as an application and dragged the app into my Dock. Now, all I have to do is click on the app in the dock, and click allow in the window that pops up (allowing the app to obtain the password for Cocktail from my keychain) and then the nested items then become immediately available. I don't have to reset any prefs regarding the appearance or behavior of the docked folders. Problem solved!

Cross-platform encrypted disk-image formats?

Is it possible to create an equivalent of an encrypted disk-image in a format that is readable under Windows? I am able to create a .dmg file using Disk Utility in MacOS and define the file-system as DOS, and encrypt it, but .dmg files are not readable under Windows. Some Win utilities claim to be able to read these, but I have not found any that work.
Is there a standard solution for creating a disk-image on my Mac that is not Mac-specific? I want to create an encrypted DOS/FAT file-system disk-image, store files in it, then open it under Windows. Does such a solution exist?
Thanks,
--- Christer

Does TrueCrypt do what you want?
(55088)

Creating a LARGE Encrypted Disk Image

Hello,
I have to encrypt a LARGE external Hard Drive for my work (a 1 Terabyte external drive, which comes to about 930 gigs to encrypt).
I have to do one of the regular encrypted disk images, not one of those expandable ones.
I know that encrypted disk images take a long time to create, as I’ve created smaller ones in the past and they take hours.
Does anyone know how long it will take to create an encrypted disk image of this size?
AND, since it will probably take quite a while, I was wondering if it is BAD for my MacBook Pro or the external drive itself to write information for this long of a period. I just want to make sure I don’t damage anything.
Thanks for any help.

I did a 400 GB one and it must have taken an hour to get the password prompt, a couple more for the creation, and another for formatting and mounting.
If you have a bed and sleep daily, as I suspect you do, start an hour before bed, enter the password and it should be done by morning.
You don't need a 900 GB image unless you have one 900 GB file which I doubt. Make one smaller one say 300, then copy it twice. The password will be the same in all 3 copies.
If you look at activity monitor not much is going on during all this so don't think the house will burn down (or your pants - see other question posted today).

Making encrypted disk image takes hours?!

Before I made a Time Machine backup, I wanted to use Disk Utility to create an encrypted disk image on an external hard drive. This way, my computer backup is password protected.
So I set the file for 200G at 128 bit encryption.
That was 12 hours ago. According to the progress bar, Disk Utility is still only one-quarter done with creating the disk image.
Is it normal for Disk Utility to take a full day (possibly two) to create a disk image of this size? Is there any way to create a password-protected disk image quicker? (And, for what it's worth, the external drive is formatted for Mac OS Extended, Journaled.)
Thanks for any advice on this...

Hi, and welcome to the forums.
I'm not quite sure just what you're trying to do.
Are you planning to have Time Machine back-up to that encrypted disk image? If so, that's not going to work. When you start Time Machine, it will create a Backups.backupdb folder on whatever drive or partition you select, then place it's backups in that folder, not in a disk image.
If you want to encrypt your whole home folder, you can use File Vault (System Preferences > Security > File Vault). That will encrypt your entire home folder. But that's almost certainly vast overkill, and has many complications of it's own. Read up on it thoroughly before deciding to do it.
If you have a few files that you want to encrypt, create a (smaller) encrypted disk image on your internal HD, in your home folder. Then copy the documents into it, and securely-delete the originals.
Then TM can back-up your entire system "as is" -- without the overhead of encrypting OSX, your apps, configuration, and everything else in your home folder, but the disk image (and it's backup copy) will still be encrypted.

Any gotchas for encrypted disk images?

Similar Messages

Maybe you are looking for