Hello. Not so much a bug but a question. Used the guide to enable OPAL on a few Samsung NVME & Sata ssd's without a problem, thanks for all the hard work you put onto this.
On an Acer Aspire XC-1760 with a very sparse AMI aptio bios version, seems Acer, having removed the ability to set passwords on disks, left OPAL encrypted disk support in. So, in practice, if the OPAL disk is locked, a window shows at boot asking to unlock the disk and for the password (three times). The password I set doesn't work here, so I just press ESC and everything continues as normal onto the Linux pba.
The question is: does anyone know why why the password fails there? Does the AMI Aptio bios adds something to the password when set by itself, like some Dell Precision bios'es used to do many years ago? Or is it the password hashing that may be different? Wondering if using the -n option with sedutil to disable hashing would make it work or is it a no-no for security reasons?
Hello. Not so much a bug but a question. Used the guide to enable OPAL on a few Samsung NVME & Sata ssd's without a problem, thanks for all the hard work you put onto this.
On an Acer Aspire XC-1760 with a very sparse AMI aptio bios version, seems Acer, having removed the ability to set passwords on disks, left OPAL encrypted disk support in. So, in practice, if the OPAL disk is locked, a window shows at boot asking to unlock the disk and for the password (three times). The password I set doesn't work here, so I just press ESC and everything continues as normal onto the Linux pba.
The question is: does anyone know why why the password fails there? Does the AMI Aptio bios adds something to the password when set by itself, like some Dell Precision bios'es used to do many years ago? Or is it the password hashing that may be different? Wondering if using the -n option with sedutil to disable hashing would make it work or is it a no-no for security reasons?