So I am making some progress on encrypting my MBP, but have some lingering questions...
1.) I was able to create an Encrypted Bootable USB Drive Clone last night.
The cloning was done via CCC, and then I encrypted things using Mountain Lion's FileVault2 interface.
So my question is this...
With a new, blank, formatted HDD in my MBP, when I boot up from my Encrypted Bootable USB Drive, it will ask me for a password.
After I enter the FIleVault2 password, and my USB Drive is "unlocked", and OS-X boots up, can I then us CCC to "clone" my blank Internal HDD?
My confusion is this...
If my USB drive is encrypted, then I am wondering if that would interfere when CCC tries to make a Bootable Clone on my blank Internal HDD...
Follow me??
2.) A question about terminology...
When you "encrypt" a HDD, and then you boot up from it, and enter the password, it becomes "unlocked".
Is the drive still considered "encrypted" at this point?
That is, I don't know if "encrypted" means "encrypted and locked" or just "encrypted"?!
Follow me??
3.) When I wanted to encrypt my Bootable USB Drive, I had to boot up from it and then use FileVault2 to encrypt it.
That was fine since I could obviously "boot" from a Bootable USB Drive.
What would I need to do if I wanted to encrypt a USB Drive or a HDD that was NOT bootable?
(For instance, maybe the USB Drive or HDD just had data on it that I wanted to protect, but no Op Sys or Bootability...)
4.) Let's say I created an Encrypted Bootable USB Drive using a "User1" account.
And then I needed to use that USB Drive to rebuild my laptop which originally only had a "User2" account on its Internal HDD.
Does it matter that a Bootable Volume is encrypted using a User Account that maybe doesn't exist on the target machine?
(It would seem to me that as long as you know the Password for the User Account that encrypted the Bootable USB you are good.)
Follow me??
Sincerely,
Debbie
1.) I was able to create an Encrypted Bootable USB Drive Clone last night.
The cloning was done via CCC, and then I encrypted things using Mountain Lion's FileVault2 interface.
So my question is this...
With a new, blank, formatted HDD in my MBP, when I boot up from my Encrypted Bootable USB Drive, it will ask me for a password.
After I enter the FIleVault2 password, and my USB Drive is "unlocked", and OS-X boots up, can I then us CCC to "clone" my blank Internal HDD?
My confusion is this...
If my USB drive is encrypted, then I am wondering if that would interfere when CCC tries to make a Bootable Clone on my blank Internal HDD...
Follow me??
2.) A question about terminology...
When you "encrypt" a HDD, and then you boot up from it, and enter the password, it becomes "unlocked".
Is the drive still considered "encrypted" at this point?
That is, I don't know if "encrypted" means "encrypted and locked" or just "encrypted"?!
Follow me??
3.) When I wanted to encrypt my Bootable USB Drive, I had to boot up from it and then use FileVault2 to encrypt it.
That was fine since I could obviously "boot" from a Bootable USB Drive.
What would I need to do if I wanted to encrypt a USB Drive or a HDD that was NOT bootable?
(For instance, maybe the USB Drive or HDD just had data on it that I wanted to protect, but no Op Sys or Bootability...)
4.) Let's say I created an Encrypted Bootable USB Drive using a "User1" account.
And then I needed to use that USB Drive to rebuild my laptop which originally only had a "User2" account on its Internal HDD.
Does it matter that a Bootable Volume is encrypted using a User Account that maybe doesn't exist on the target machine?
(It would seem to me that as long as you know the Password for the User Account that encrypted the Bootable USB you are good.)
Follow me??
Sincerely,
Debbie