Hi everyone,
I've been procrastinating on this for a while now, but I want to set up encryption on my Samsung 840 PRO SSD. I have this drive in my ASUS UX32VD-DH71-CB Ultrabook, which, sadly, does not have hardware TPM (I learnt this yesterday by contacting ASUS).
I also recently learnt the (not so) hard way that Diskcryptor, a TrueCrypt alternative for GPT drives, doesn't work with Windows 8 installations.
I'd also like to mention that, knowing TrueCrypt didn't work with GPT/EFI, I initially formatted my SSD using MBR, so using TrueCrypt is always an option.
I'd like to know if t is possible to check whether or not a my SSD is effectively encrypted, or simply ATA password protected when I input a password through the BIOS.
--------------------
From my understanding, and please correct me if I am wrong, one needs TPM in order to utilize the hardware encryption on SSDs... If this is the case, I will turn to TrueCrypt, as my processor supports AES-NI and I'd rather keep TRIM than have plausible deniability.
--------------------
Thanks for the help, all, and apologies if this has been previously answered.
I've been procrastinating on this for a while now, but I want to set up encryption on my Samsung 840 PRO SSD. I have this drive in my ASUS UX32VD-DH71-CB Ultrabook, which, sadly, does not have hardware TPM (I learnt this yesterday by contacting ASUS).
I also recently learnt the (not so) hard way that Diskcryptor, a TrueCrypt alternative for GPT drives, doesn't work with Windows 8 installations.
I'd also like to mention that, knowing TrueCrypt didn't work with GPT/EFI, I initially formatted my SSD using MBR, so using TrueCrypt is always an option.
I'd like to know if t is possible to check whether or not a my SSD is effectively encrypted, or simply ATA password protected when I input a password through the BIOS.
--------------------
From my understanding, and please correct me if I am wrong, one needs TPM in order to utilize the hardware encryption on SSDs... If this is the case, I will turn to TrueCrypt, as my processor supports AES-NI and I'd rather keep TRIM than have plausible deniability.
--------------------
Thanks for the help, all, and apologies if this has been previously answered.