From: Embedded Devel <yocto@optimcloud.com>
To: Måns <mans.zigher@gmail.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization] Docker and GPLv3
Date: Fri, 04 Feb 2022 14:42:20 +0000 [thread overview]
Message-ID: <1643985053428.3389501462.529681158@optimcloud.com> (raw)
In-Reply-To: <CAEhQi8mFNmsjymm6tsFCekZpJzXjbibkdHXA4f0KLP2FHZwnCg@mail.gmail.com>
On Friday 04 February 2022 21:23:18 PM (+07:00), Måns wrote:
> Hi,
>
> Well, does GPLv3 not require that a customer should be able to build
> the GPLv3 like bash and deploy it to the target? It is not directly
> secure-boot but the customer has a boot up sequence that starts with
> secure boot and then the rootfs needs to be signed. So it would not be
> possible to open up the device to allow a customer to deploy his own
> version of bash on the target. But I might have misunderstood GPLv3. I
> am not an expert.
>
> BR
> Måns Zigher
ermmm no... my understanding is if a device is bootlocked.. grub or secure-boot, then the vendor only needs to provide a way a client having ownership of the device
can make, rebuild, duplicate, circumvent the secure-boot. ie... make it undoable/bypassable and as long as they allow users to install their own secure boot keys
now im not LAWYER .... However.... if a client can regenerate keys/bootloader/image then i believe your safe.
>
> Den fre 4 feb. 2022 kl 15:19 skrev Embedded Devel <yocto@optimcloud.com>:
> >
> >
> >
> > On Friday 04 February 2022 15:53:42 PM (+07:00), Mans Zigher wrote:
> >
> > > Hi,
> > >
> > > A client of mine wants to have docker on it's product and they are
> > > having secure boot enabled which prevents us from having any GPLv3
> > > licensed code on the target.
> > Okay, wait, why does enabling secure-boot prevent including GPLv3 packages??
> > Ive never heard this before.
>
--
Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com
prev parent reply other threads:[~2022-02-04 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 8:53 Docker and GPLv3 Måns
2022-02-04 14:15 ` [meta-virtualization] " Bruce Ashfield
2022-02-04 14:30 ` Måns
2022-02-04 15:03 ` Joakim Roubert
2022-02-04 15:29 ` Mikko.Rapeli
2022-02-07 7:36 ` Måns
2022-02-04 14:19 ` Embedded Devel
2022-02-04 14:23 ` Måns
2022-02-04 14:42 ` Embedded Devel [this message]
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=1643985053428.3389501462.529681158@optimcloud.com \
--to=yocto@optimcloud.com \
--cc=mans.zigher@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.org \
/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.