All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Stefano Garzarella <sgarzare@redhat.com>, coconut-svsm@lists.linux.dev
Subject: Re: TCG TPM license issue
Date: Fri, 23 Jan 2026 22:06:46 +0000	[thread overview]
Message-ID: <aXPw9k6pJJwAoSNo@redhat.com> (raw)
In-Reply-To: <6146dc59fed504a84db645cde56c3b85082aff0f.camel@HansenPartnership.com>

On Fri, Jan 23, 2026 at 02:15:49PM -0500, James Bottomley wrote:
> On Fri, 2026-01-23 at 11:02 +0100, Stefano Garzarella wrote:
> > Hi all,
> > it seems the license of the TCG TPM reference implementation that we
> > are using to emulate the vTPM in SVSM is not exactly BSD but a
> > variant of it.
> > 
> > For some distro, like Fedora, this could be an issue. See
> > https://gitlab.com/fedora/legal/fedora-license-data/-/issues/716
> 
> The problem clause is a conditional statement about the origin of the
> code and not part of the licence, so I don't believe it modifies the
> BSD-2-Clause nature of the implementation in any way.

That feels too convenient as a rationalization. Why would it not have 
been left as an unmodified BSD-2-Clause license document without this
extra language added ? There's some intent behind including it. It
comes across like a attempt to make a new BSD variant, similar in style
to the BSD-3-Clause-Clear (also forbidden in Fedora).

> Additionally, just in the interest of fair dealing Fedora can't
> disapprove of this this disclaimer in coconut, but perfectly fine with
> it in another project they're already shipping:
> 
> https://packages.fedoraproject.org/pkgs/libtpms/libtpms/index.html
> 
> which has a slightly different form of the disclaimer (inherited
> directly from the TCG) which seems to be a bit stronger in terms of
> modifying the licence:
> 
> https://github.com/stefanberger/libtpms/blob/master/LICENSE

FWIW, that is referred to as the "TCGL" license in Fedora terminology
and that is also denoted as forbidden for further usage. The libtpms
package was accepted into Fedora some 15 years ago, and after the
change in rules, it was decided to grant it an exception to allow it
to remain

  https://gitlab.com/fedora/legal/fedora-license-data/-/blob/main/data/LicenseRef-TCGL.toml

Yes, that is somewhat unfair to other packages that have the same or similar
license, but that's the tradeoff Fedora has chosen to make in this tricky
scenario.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|


  reply	other threads:[~2026-01-23 22:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23 10:02 TCG TPM license issue Stefano Garzarella
2026-01-23 19:15 ` James Bottomley
2026-01-23 22:06   ` Daniel P. Berrangé [this message]
2026-01-24 16:57     ` James Bottomley
2026-01-27 17:06   ` Stefano Garzarella

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-all 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=aXPw9k6pJJwAoSNo@redhat.com \
    --to=berrange@redhat.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=coconut-svsm@lists.linux.dev \
    --cc=sgarzare@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.