You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see no option in the current code for anything beyond the "SECURE ERASE" command invocation.
Per the NIST standard (NIST Special Publication 800-88, Revision 1, Guidelines for Media Sanitization), it's preferred to use the 'SANITIZE" command over "SECURE ERASE" where available.
I would request this option be supported in a future release.
It would also be advisable to allow Cryptographic Erase, where SED has been used.
Enhanced Erase mode. The ATA Sanitize Device feature set commands are preferred
over the over the ATA Security feature set SECURITY ERASE UNIT command when
supported by the ATA device.
The text was updated successfully, but these errors were encountered:
tbzatek
changed the title
Feature Request: Add SAS/SATA/NVMe "SANITIZE" command option for secure erasure
RFE: Add SAS/SATA/NVMe "SANITIZE" command option for secure erasure
Jan 1, 2024
Agree, this would be useful. No promises when this actually happens, patches welcome.
The NVMe Sanitize command is available since the last release. Let us know if it fits your needs. Support for additional TPs like TP4152 may be added in the future.
There's currently no specific support for SAS drives (like the org.freedesktop.UDisks2.Drive.Ata interface). #1007 will be needed first.
Also, there's been a similar secure erase request, although that's about overwrite methods: #971
I see no option in the current code for anything beyond the "SECURE ERASE" command invocation.
Per the NIST standard (NIST Special Publication 800-88, Revision 1, Guidelines for Media Sanitization), it's preferred to use the 'SANITIZE" command over "SECURE ERASE" where available.
I would request this option be supported in a future release.
It would also be advisable to allow Cryptographic Erase, where SED has been used.
The text was updated successfully, but these errors were encountered: