Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1545686

Re: [PATCH v3 2/5] lib: Add Sed-opal library

From Christoph Hellwig <hch@infradead.org>
Newsgroups linux.kernel
Subject Re: [PATCH v3 2/5] lib: Add Sed-opal library
Date 2016-12-21 10:50 +0100
Message-ID <sQLH3-1Fi-21@gated-at.bofh.it> (permalink)
References <sQc6B-3He-3@gated-at.bofh.it> <sQc6B-3He-33@gated-at.bofh.it> <sQn21-2sK-1@gated-at.bofh.it> <sQALD-384-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Tue, Dec 20, 2016 at 03:07:46PM -0700, Jon Derrick wrote:
> > This pretty much seem to contain the OPAL protocol defintions, so why
> > not opal_proto.h?
> Since there might eventually be a whole class of opal-like sed
> protocols, why does it make more sense to have opal_proto.h instead of
> sed-opal.h or some variation? This is similar to how leds-*.h look to
> me. Although I agree that sed-ATA.h would be dishonest since ATA
> security doesn't imply a self-encrypting-disk.

As far as I can tell the NVMe / SCSI / ATA security landscape looks
like:

 - ATA security - specified in ATA, kinda implicitly referenced by SPC
   and then even more implitly in NVMe.  Actually implemented in various
   NVMe consumer devices because OEMs insist on it.  Basically just
   a trivial plain text password lock/unlock.

 - TCG OPAL including the subsets OPALite and Pyrite, whereas the latter
   is just the above lock/unlock in a TCG way.

 - TCG Enterprise SSC

I think it's pretty obvious that ATA security should be something on
it's own.  OPALite and Pyrite are strict subsets of OPAL, so having them
in something named opal shouldn't be surprising.  The big question
is what to do about Enterprise SSC.  Which has some overlaps with OPAL
but also major differences, so keeping it separate if we ever have to
implement it (I hope we don't) would be best.

> I'm on board with this if you think we won't have enough different, but
> similar, SED protocols to justify the indirection. In that case you can
> ignore the above comment as well.

This goes back to the above.  The only thing that is not a strict subset
of OPAL but kinda sorta similar is TCG Enterprise SSC, but my preference
would be to ignore it, and the second best preference would be to keep
it separate.

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH v3 0/5] SED OPAL Library Scott Bauer <scott.bauer@intel.com> - 2016-12-19 20:50 +0100
  Re: [PATCH v3 2/5] lib: Add Sed-opal library Keith Busch <keith.busch@intel.com> - 2016-12-19 22:30 +0100
    Re: [PATCH v3 2/5] lib: Add Sed-opal library Christoph Hellwig <hch@infradead.org> - 2016-12-20 07:10 +0100
  Re: [PATCH v3 2/5] lib: Add Sed-opal library Al Viro <viro@ZenIV.linux.org.uk> - 2016-12-20 08:00 +0100
  Re: [PATCH v3 2/5] lib: Add Sed-opal library Christoph Hellwig <hch@infradead.org> - 2016-12-20 08:30 +0100
    Re: [PATCH v3 2/5] lib: Add Sed-opal library Jon Derrick <jonathan.derrick@intel.com> - 2016-12-20 23:10 +0100
      Re: [PATCH v3 2/5] lib: Add Sed-opal library Christoph Hellwig <hch@infradead.org> - 2016-12-21 10:50 +0100
    Re: [PATCH v3 2/5] lib: Add Sed-opal library Scott Bauer <scott.bauer@intel.com> - 2016-12-20 23:10 +0100
      Re: [PATCH v3 2/5] lib: Add Sed-opal library Christoph Hellwig <hch@infradead.org> - 2016-12-21 10:50 +0100

csiph-web