This is not Samsung’s fault. The IEEE 1667 standard does not support NVMe yet.

> IEEE 1667 TCG Transport Silo is a requirement for “eDrive” support
>> eDrive in 30 seconds:
>>> Starting with Windows 8, MS BitLocker is able to manage SEDs that implement Opal 2.00, Single User Mode Feature Set, and the IEEE 1667 TCG Transport Silo

> IEEE 1667 has begun working on a IEEE 1667 transport technical proposal for NVMe
>> Enables general access to IEEE 1667 silos over NVMe, including 1667 TCG transport Silo
>>> TCG Transport Silo – alternate transport for TCG Opal commands
>>Enables management of Windows eDrive for NVMe Opal SEDs which use Opal 2.00

On modern SSDs, even the ATA password (what Samsung calls “Class 0”) is secure since the keys are protected by the actual password. Most motherboards do not allow you to set the ATA password anymore. However, if you do set the ATA password using a compatible motherboard or utliity, the encryption should be just as secure as TCG Opal pre-boot authentication. Most motherboards will prompt you for the ATA password if a locked drive is connected, even if they don’t allow you to set the password in the first place. The 950 PRO (and the 960 PRO) supports “Class 0” so this is an alternative to a TCG Opal pre-boot environment which usually delays the boot time considerably. The disadvantge is it can only lock the whole drive and not individual blocks (partitions) like TCP Opal and eDrive.

I will take a look into sedutil. Thanks for bringing this option to my attention.

The 960 PRO spec sheet says it supports TCP Opal, but doesn’t mention IEEE 1667. This means BitLocker will fall back to software encryption. You must use a 3rd party tool like “sedutil” to enable hardware encryption with pre-boot authentication.

I know my Evo 850 has the functionality you’re asking for, it’s a shame 950 does not. Also, I want to make sure you understood what i said on my earlier post; when you use Windows 10, and enable “encrypted drive” with BITLockER, the encryption is not performed by software. Under that scenario the encryption is handled by the controller on the SSD.

I think the “government” is trying to stick it to “us”. First they killed TrueCrypt and now they’re discretely trying to undermine all other forms of disk encryption 😉 *wink*wink* It’s amazing how PGP did not get AXEd in the 90’s.

How will we safely whisper “”King Midas has the ears of an ass.” without full disk encryption ;))

As for me enabling HD password on the BIOS is sufficient as the data written on the flash is already encrypted and it will require someone more sophisticated than a computer savvy punk to replace the controller on the disk and even so, he will be greeted with encrypted data as the keys won’t match with the one on the new disk controller. Again; “King Midas has the ears of an ass.”