linux-kernel - Re: [PATCH] scsi: use ATA-12 pass-thru for OPAL as fallback

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 16 Oct 2023 15:27:30 +0200
From:   Christoph Hellwig <hch@....de>
To:     Milan Broz <gmazyland@...il.com>
Cc:     Damien Le Moal <dlemoal@...nel.org>,
        Christoph Hellwig <hch@....de>, linux-scsi@...r.kernel.org,
        jejb@...ux.ibm.com, martin.petersen@...cle.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scsi: use ATA-12 pass-thru for OPAL as fallback

On Mon, Oct 16, 2023 at 02:46:03PM +0200, Milan Broz wrote:
> The problem is that we (for simplicity) decided to use kernel SED-ioctl interface that
> internally wraps OPAL command to SCSI SECURITY command only. It means, that all devices

No, it doesn't.  It uses the properly specified protocol for each
layer.  That is NVMe uses NVMe Security Send/Receive, SCSI uses the
SCSI protocol, and libata translats for ATA devices.

> that can use ATA-12 just cannot work with this kernel interface (unlike userspace which
> can decide which wrapper to use).

It supports all devices that actually speak ATA perfectly fine, take
a look at ata_scsi_security_inout_xlat.

>
> And IMO it is not correct - if it was designed only for some servers with directly connected
> devices, then it is really not generic OPAL support. It should work for any hw that supports it.

Let's get off your crack pipe before we continue.  It is designed and
implemented to support the security protocols exactly as spec'ed.

You seem to have found devices that claim to be SCSI, but actually
require ATA passthrough for security.  That's no secret cabal to lock
out non-server hardware but just proper protocol design.

> For USB, it actually works quite nice with the patch (ignoring usual bugs in firmware).

So move it into usb if you can convince the usb maintainers that they
are fine with it.

>
>>
>> Note that nowhere in your patch do you test if you are talking to an ATA device.
>
> Yes, I know. I expected the command to be rejected if not supported.

Good luck.  Cheap storage hardware trips up on unknown commands all the
time.

> IMO it is quite similar to discard/TRIM support...

Where we also don't support weird ATA commands directly from sd
for good reason.