search

Drive-Trust-Alliance / sedutil

DTA sedutil Self encrypting drive software
613 stars 237 forks source link

Support for NVMe Namespaces #371

Open mateoconlechuga opened 3 years ago

mateoconlechuga commented 3 years ago

Is there currently support for NVMe namespaces, as described in this document? https://trustedcomputinggroup.org/wp-content/uploads/TCG_Storage_Configurable_Namespace_Locking-_NS_and_LUN_v1p01_r1p11_31mar2021.pdf

I'm curious if I can configure locking regions for individual namespaces and how that works within the scope of the LBA regions defined by the Opal specification.

r0m30 commented 3 years ago

I have not looked into namespace locking at all. Namespaces have interesting possibilities but at this point it's low on the priority list.

mateoconlechuga commented 3 years ago

That's all right; just curious! It amazes me how many specifications on top of other specifications there are -- it's rather insane.

neo125874 commented 2 years ago

@r0m30 @mateoconlechuga Hi, did you successfully setup-locking-range 1/2/.... & lock/unlock on windows nvme drive? we tried 1.setup-locking-range 1, 2. enable-locking-range, 3. set-locking-range, and reboot, but the nvme drive became raw disk even if we disable-locking-range, any suggestion? thanks.

tonsui commented 2 years ago

Under Windows, you need to use SCSI sendCmd, lukefor has implementation in this fork: https://github.com/lukefor/sedutil/tree/windows_nvme