|
|
Create multiple nested secure disk images
AES 128 is rated by the US government for Secret (but not Top Secret) documents. That means that is is unreasonable to think that someone without extraordinary resources (think NSA level resources) could break the encryption within a reasonable amount of time (think days of work) with current common hardware.
Create multiple nested secure disk images
And, WHAT exactly is wrong with my tin-foil hat?
Create multiple nested secure disk images
This brings up a good point no one seems to know - what are the option switches for "crypto_method" used with hdiutil -encryption? How would you go about making an AES 192 encrypted image. I have searched far and wide for that info and can't find it anywhere....
Create multiple nested secure disk images
All one needs to do to break an ordinary encrypted disk image is guess a single password. Given the way most people choose their passwords, the task of correctly guessing them is well within the reach of the average hacker. AES-192 is no more secure than AES-128 if your password is "hello".
Create multiple nested secure disk images
just a short comment on this:
"Given the way most people choose their passwords"
Anyone trying to protect their files should use good enough passwords in the first place! Why do you suppose that those who take the time to nest their files deep inside encrypted disk images does not take the time to use a good password? I use only simple AES-128 protected disk images (4380 MB so they fit on a DVD), but with a 16 character long, randomly chosen string as a password. Next step would be to use a few more characters, and..... ps: never use the AES protected sparseimage format! It gets corrupt in case of a system crash never to be mounted again! |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.08 seconds |
|