From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Clement Ramirez <ramirez.clement3@gmail.com>
Cc: Martin Bark <martin@barkynet.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/2] package/connman: fix CVE-2023-28488
Date: Sun, 20 Aug 2023 11:14:31 +0200 [thread overview]
Message-ID: <20230820091431.GG1778688@scaer> (raw)
In-Reply-To: <20230818200529.41913-1-ramirez.clement3@gmail.com>
Clément, Al,
On 2023-08-18 22:05 +0200, Clement Ramirez spake thusly:
> This patch series is designed to fix the CVE-2023-28488:
> - The first commit backports the CVE-2023-28488 patch fix onto the 1.41
> connman version.
> - The second commit bumps connman to 1.42 and removes the previous
> deprecated patches that introduced fixes now present in the 1.42.
> This way the first commit can be used to fix the CVE in LTS releases,
> and the second one for future releases of Buildroot.
Since the oldest maintenance branch we have already uses connman 1.41,
we can just backport the version bump to get all the security fixes.
So I squashed the two commits ogether,
Applied to master, thanks.
Regards,
Yann E. MORIN.
> Clement Ramirez (2):
> package/connman: fix CVE-2023-28488
> package/connman: security bump version to 1.42
>
> .checkpackageignore | 3 -
> ...-gweb-Fix-OOB-write-in-received_data.patch | 36 ----
> ...-reference-counter-to-portal-context.patch | 142 --------------
> ...spr-Update-portal-context-references.patch | 175 ------------------
> package/connman/connman.hash | 2 +-
> package/connman/connman.mk | 9 +-
> 6 files changed, 2 insertions(+), 365 deletions(-)
> delete mode 100644 package/connman/0001-gweb-Fix-OOB-write-in-received_data.patch
> delete mode 100644 package/connman/0002-wispr-Add-reference-counter-to-portal-context.patch
> delete mode 100644 package/connman/0003-wispr-Update-portal-context-references.patch
>
> --
> 2.34.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-20 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 20:05 [Buildroot] [PATCH 0/2] package/connman: fix CVE-2023-28488 Clement Ramirez
2023-08-18 20:05 ` [Buildroot] [PATCH 1/2] " Clement Ramirez
2023-08-18 20:05 ` [Buildroot] [PATCH 2/2] package/connman: security bump version to 1.42 Clement Ramirez
2023-08-20 9:14 ` Yann E. MORIN [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=20230820091431.GG1778688@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=martin@barkynet.com \
--cc=ramirez.clement3@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox