sedutil icon indicating copy to clipboard operation
sedutil copied to clipboard

SEDutil: For Intel and AMD Ryzen Systems

Results 47 sedutil issues
Sort by recently updated
recently updated
newest added

When using the rescue system RESCUE64-1.15-5ad84d8.img, which was booted within a ventoy usb, onto a Dell XPS 9575 i7 with a 4k screen, the typed text commands from the terminal...

TLDR -> SEDutil works fine with Windows 11 if the PC is secure boot capable and you have secure boot disabled. I thought that Windows 11 would not work with...

- On reboot, after activating the SSD(Crucial MX500) locking with the "sedutil-cli" tool, the unlocking password prompt does not appear. - the locking process goes as expected, following the steps...

Very like [this](https://github.com/Drive-Trust-Alliance/sedutil/issues/222) issue, I'm getting: > Session start failed rc = 136 > Unable to start Unauthenticated session > EndSession Failed > Unable to read MSID password > Initial...

I have a Self Encrypted Disk (SED). I'd like to use `sedutil` to lock the disk, but I want the password to be sealed in the TPM module on board...

Can you please hint if `sedutil-cli` is really working? There is not a lot of documentation on the web. I've read carefully and followed the Drive-Trust-Alliance/sedutil guide [Encrypting your drive](https://github.com/Drive-Trust-Alliance/sedutil/wiki/Encrypting-your-drive)...

Fix typo in readme

Haven't found this info anywhere, so I just add it FYI: When installing additional OPAL-capable drives to the system simply follow _for each drive_ the same full* procedure as for...

These outputs were generated on the same hardware running different operating systems. **FreeBSD 13.2-RELEASE** ``` # uname -a FreeBSD topaz 13.2-RELEASE FreeBSD 13.2-RELEASE releng/13.2-n254617-525ecfdad597 GENERIC amd64 # ./sedutil-cli --scan Scanning...

Looking at the code I noticed that `access()` is being called with `"/dev/sda"` rather than `devref`. Might cause problems, especially on systems that don't have a /dev/sda! Suggested fix below:...