From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yoann Congal <yoann.congal@smile.fr>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] dropbear: Clarify LICENSE and drop PD
Date: Tue, 30 Jun 2026 07:42:11 +0100 [thread overview]
Message-ID: <82485f53d8cdfc2fded0f3786cbe97fb105e9902.camel@linuxfoundation.org> (raw)
In-Reply-To: <DJLWBE1WSDSN.G0FEJAKOMOUI@smile.fr>
On Tue, 2026-06-30 at 00:44 +0200, Yoann Congal wrote:
> On Tue Jun 2, 2026 at 5:00 PM CEST, Richard Purdie via lists.openembedded.org wrote:
> > The "public-domain" code has a MIT license header so we can remove
> > that from LICENSE (MIT is already listed).
> >
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> > meta/recipes-core/dropbear/dropbear_2025.89.bb | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-core/dropbear/dropbear_2025.89.bb b/meta/recipes-core/dropbear/dropbear_2025.89.bb
> > index 957a0901fb0..ece065265ff 100644
> > --- a/meta/recipes-core/dropbear/dropbear_2025.89.bb
> > +++ b/meta/recipes-core/dropbear/dropbear_2025.89.bb
> > @@ -5,7 +5,8 @@ SECTION = "console/network"
> >
> > # some files are from other projects and have others license terms:
> > # public domain, OpenSSH 3.5p1, OpenSSH3.6.1p2, PuTTY
> > -LICENSE = "MIT & BSD-3-Clause & BSD-2-Clause & PD"
> > +# The 'public-domain' file is headered as MIT
> > +LICENSE = "MIT & BSD-3-Clause & BSD-2-Clause"
> > LIC_FILES_CHKSUM = "file://LICENSE;md5=25cf44512b7bc8966a48b6b1a9b7605f"
>
> While reviewing backporting this patch for scarthgap, I've look at the
> licences of dropbear:
> The "'public-domain' file headered as MIT" is (I think):
> https://github.com/mkj/dropbear/blob/DROPBEAR_2026.91/src/curve25519.c
> (indeed MIT header)
>
> But:
> * vendored libtommcrypt is "PD OR WTFPL"
> https://github.com/mkj/dropbear/blob/DROPBEAR_2026.91/libtomcrypt/LICENSE
> * vendored libtommath is "Unlicense"
> https://github.com/mkj/dropbear/blob/DROPBEAR_2026.91/libtommath/LICENSE
> ... is that OK that those don't appear in LICENSE?
>
> If yes, then the argument is still valid for scarthgap and I'll will
> backport.
Well spotted, I think you're right that I didn't get this quite right.
It should be:
"MIT & BSD-3-Clause & BSD-2-Clause & (PD | WTFPL) & Unlicense"
assuming those libs are always used in the build.
We should probably just make it:
"MIT & BSD-3-Clause & BSD-2-Clause & WTFPL & Unlicense"
since PD just causes us pain and WTFPL is effectively the alternative.
Cheers,
Richard
next prev parent reply other threads:[~2026-06-30 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 15:00 [PATCH] dropbear: Clarify LICENSE and drop PD Richard Purdie
2026-06-29 22:44 ` [OE-core] " Yoann Congal
2026-06-30 6:42 ` Richard Purdie [this message]
2026-06-30 7:34 ` Yoann Congal
2026-06-30 13:50 ` Yoann Congal
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=82485f53d8cdfc2fded0f3786cbe97fb105e9902.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=yoann.congal@smile.fr \
/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.