From: Steve Sakoman <steve@sakoman.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][kirkstone 6/7] ppp: Add RSA-MD in LICENSE
Date: Wed, 17 Apr 2024 15:33:12 -0700 [thread overview]
Message-ID: <CAOSpxdacWHTw5sb4nNQ0rxTOjqrZC0gQi=Aa6Xz0-XFqSb1pig@mail.gmail.com> (raw)
In-Reply-To: <7b6c45a05dde783826b5a73b1bdb0a821efd0701.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]
On Wed, Apr 17, 2024, 2:33 PM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
> On Wed, 2024-04-17 at 13:35 -0700, Steve Sakoman via
> lists.openembedded.org wrote:
> > From: Poonam Jadhav <ppjadhav456@gmail.com>
> >
> > ppp package has "RSA Data Security" license text
> > in Message-Digest Algorithm source file md5.c and md4.c
> > Add RSA-MD in LICENSE field for ppp package
> >
> > Signed-off-by: Poonam Jadhav <poonam.jadhav@kpit.com>
> > Signed-off-by: Steve Sakoman <steve@sakoman.com>
> > ---
> > meta/recipes-connectivity/ppp/ppp_2.4.9.bb | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
> b/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
> > index 7e3ae43b58..b7f71b673d 100644
> > --- a/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
> > +++ b/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
> > @@ -5,7 +5,7 @@ SECTION = "console/network"
> > HOMEPAGE = "http://samba.org/ppp/"
> > BUGTRACKER = "http://ppp.samba.org/cgi-bin/ppp-bugs"
> > DEPENDS = "libpcap openssl virtual/crypt"
> > -LICENSE = "BSD-3-Clause & BSD-3-Clause-Attribution & GPL-2.0-or-later &
> LGPL-2.0-or-later & PD"
> > +LICENSE = "BSD-3-Clause & BSD-3-Clause-Attribution & GPL-2.0-or-later &
> LGPL-2.0-or-later & PD & RSA-MD"
> > LIC_FILES_CHKSUM =
> "file://pppd/ccp.c;beginline=1;endline=29;md5=e2c43fe6e81ff77d87dc9c290a424dea \
> >
> file://pppd/plugins/passprompt.c;beginline=1;endline=10;md5=3bcbcdbf0e369c9a3e0b8c8275b065d8 \
> >
> file://pppd/tdb.c;beginline=1;endline=27;md5=4ca3a9991b011038d085d6675ae7c4e6 \
> >
>
> This isn't in master yet!
>
Good catch! I'll text this patch and request that out be sent for master.
Steve
>
[-- Attachment #2: Type: text/html, Size: 3512 bytes --]
next prev parent reply other threads:[~2024-04-17 22:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 20:35 [OE-core][kirkstone 0/7] Patch review Steve Sakoman
2024-04-17 20:35 ` [OE-core][kirkstone 1/7] libssh2: fix CVE-2023-48795 Steve Sakoman
2024-04-17 20:35 ` [OE-core][kirkstone 2/7] ruby: fix CVE-2024-27281 Steve Sakoman
2024-04-17 20:35 ` [OE-core][kirkstone 3/7] rust: add CVE_CHECK_IGNORE for CVE-2024-24576 Steve Sakoman
2024-04-17 20:35 ` [OE-core][kirkstone 4/7] nghttp2: Fix CVE-2024-28182 Steve Sakoman
2024-04-17 20:35 ` [OE-core][kirkstone 5/7] valgrind: skip intermittently failing ptest Steve Sakoman
2024-04-17 20:35 ` [OE-core][kirkstone 6/7] ppp: Add RSA-MD in LICENSE Steve Sakoman
2024-04-17 21:33 ` Richard Purdie
2024-04-17 22:33 ` Steve Sakoman [this message]
[not found] ` <17C7320A63076F69.11286@lists.openembedded.org>
2024-04-17 22:57 ` Steve Sakoman
2024-04-17 20:35 ` [OE-core][kirkstone 7/7] systemd: Fix vlan qos mapping Steve Sakoman
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='CAOSpxdacWHTw5sb4nNQ0rxTOjqrZC0gQi=Aa6Xz0-XFqSb1pig@mail.gmail.com' \
--to=steve@sakoman.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).