public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: Joakim Bech <joakim.bech@linaro.org>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	edk2-devel@lists.01.org, tee-dev@lists.linaro.org,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Matteo.Carlini@arm.com, Achin.Gupta@arm.com, udit.kumar@nxp.com,
	Liming Gao <liming.gao@intel.com>
Subject: Re: [PATCH v2 1/2] MdePkg/IndustryStandard: Add Global Plaform header file
Date: Fri, 28 Sep 2018 12:50:24 +0100	[thread overview]
Message-ID: <20180928115024.rcvq7ybb2uwdczol@bivouac.eciton.net> (raw)
In-Reply-To: <CAFA6WYMStqe96uQu-H9dPtmxsNA3wqD8Q1EuOKdnAWoTNnePPg@mail.gmail.com>

Hi Sumit,

On Fri, Sep 28, 2018 at 11:59:33AM +0530, Sumit Garg wrote:
> > > Please help to answer below query from Michael regarding licensing
> > > concerns for using Global Platform specs content in OP-TEE.
> >
> > This dates back to ~2014 before OP-TEE had been pushed as an open source
> > project and indeed the click-through license was one thing that was
> > discussed before we decided to publish this. Having that said, the legal
> > people at ST (back then the project was owned by ST) concluded that we
> > could use the GP click-through license for the APIs, this is a
> > copy/paste from an email discussion with ST (in 2014).
> >
> > "On the legal side, one week ago our legal dedicated to this matter
> > wrote “Progress! Finally, having discussed with colleagues, we have
> > concluded that we can use the GP click-through license for the APIs.
> > Therefore I just need to tidy up the following points and we will be
> > able to provide both the CLA and the license terms for the distribution
> > quite quickly […].”
> >
> > I don't know how the discussion went inside ST nor who the legal person
> > was, but since ST had people on GlobalPlatform boards back then, I
> > suppose that the ST legal people went that way. The only way to find out
> > more about this is to talk directly to ST legal people who were involved
> > in this back in the days.
> 
> Thanks Joakim for this info.
> 
> Mike,
> 
> Please share your views on this and if we could include content from
> Global Platform spec into MdePkg as an industry standard.

Having had a discussion about this, the bit that concerns us the most
is the export restrictions clause of the click-through license which
contains the very unfortunate part "or any product complying with the
Specification.".

Someone must have thought this interface defines cryptography, rather
than an API through which to call cryptography functions.

I don't like it, but without a change in that license I don't see how
we can include this interface in edk2. One workaround would be to
publish this in a separate repository on https://github.com/OP-TEE/
which could be included in builds using PACKAGES_PATH (like we do with
edk2-platforms and edk2-non-osi).

/
    Leif


  reply	other threads:[~2018-09-28 11:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27 11:50 [PATCH v2 0/2] Add ArmPkg/Optee library APIs Sumit Garg
2018-08-27 11:50 ` [PATCH v2 1/2] MdePkg/IndustryStandard: Add Global Plaform header file Sumit Garg
2018-09-21 23:15   ` Ard Biesheuvel
2018-09-24  8:26     ` Ard Biesheuvel
2018-09-24 16:49       ` Kinney, Michael D
2018-09-25  8:27         ` Sumit Garg
2018-09-25  8:31           ` Ard Biesheuvel
2018-09-26 18:02             ` Kinney, Michael D
2018-09-27 12:10               ` Sumit Garg
     [not found]                 ` <20180927125156.3ylxviy5lnu5pm4w@debby>
2018-09-28  6:29                   ` Sumit Garg
2018-09-28 11:50                     ` Leif Lindholm [this message]
2018-08-27 11:50 ` [PATCH v2 2/2] ArmPkg/OpteeLib: Add APIs to communicate with OP-TEE Sumit Garg
2018-09-12  7:28 ` [PATCH v2 0/2] Add ArmPkg/Optee library APIs Sumit Garg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180928115024.rcvq7ybb2uwdczol@bivouac.eciton.net \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox