search

oom-is / sedutil

DTA sedutil Self encrypting drive software
3 stars 1 forks source link

Builds from Integ: 20191015 snapshot of sedutil-cli Windows and Linux (UEFI) produce different hashes #23

Open Thireus opened 4 years ago

Thireus commented 4 years ago

It appears the hashes produced by EFI Opal UEFI64-1.15.1-14-g5895605.img.gz and Windows sedutil-cli Windows_sedutil-cli_013dd9d.zip are different. Therefore, if the drive is initialised on Windows, it cannot be unlocked on Linux and vice-versa.

I have also altered the EFI so I can execute sedutil-cli manually from UEFI shell prompt, I double checked the password, but no luck... the drive won't accept the password.

Ultimately, I ended up removing OPAL and initialising the drive directly via UEFI using the sedutil-cli provided there. I'm curious to know why the sedutil-cli provided in the UEFI doesn't generate the same hashes.

This is the sedutil-cli present in the UEFI64-1.15.1-14-g5895605.img.gz (md5): 1767b718c52e7ab61f3afbfb18bb8362 rootfs/sbin/sedutil-cli

Steps to reproduce the issue:

  1. Boot Windows
  2. Initialise OPAL on drive & lock it using sedutil-cli: https://github.com/oom-is/sedutil/releases/download/v1.16-beta1/Windows_sedutil-cli_013dd9d.zip
  3. Verify drive can be unlocked with password
  4. Shutdown computer
  5. Obtain, modify init script to launch sh
  6. Boot EFI: https://github.com/oom-is/sedutil/releases/download/v1.16-beta1/UEFI64-1.15.1-14-g5895605.img.gz
  7. Try to unlock drive with same password from sedutil-cl
  8. Unlock fails...
  9. Boot windows and unlock drive with same password... Unlock works...