From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Asterisk for Buildroot 2024.02+
Date: Mon, 18 Dec 2023 17:49:40 +0100 [thread overview]
Message-ID: <ZYB4JBDLiHq0rbWA@landeda> (raw)
In-Reply-To: <87wmtb8y76.fsf@48ers.dk>
Peter, All,
On 2023-12-18 13:58 +0100, Peter Korsgaard spake thusly:
> FYI,
>
> The Asterisk version in Buildroot (16.30.1) is EOL upstream since
> October:
>
> https://docs.asterisk.org/About-the-Project/Asterisk-Versions/
>
> Recently a high severity (CVSS 7.5) security vulnerability was found:
>
> https://github.com/asterisk/asterisk/security/advisories/GHSA-hxj9-xwr8-w8pq
>
> 16.x is most likely also affected, but no patch is available
> upstream. We really need to move to a supported version (E.G. 18.x)
> before the 2024.02 release. Is there interest in doing so or should the
> package be dropped instead?
I unfortunately no longer have any need for asterisk, and I have no way
of testing a new version any longer either.
So, unless someone steps up, we'll have to drop the package.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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-12-18 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 12:58 [Buildroot] Asterisk for Buildroot 2024.02+ Peter Korsgaard
2023-12-18 16:49 ` 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=ZYB4JBDLiHq0rbWA@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=peter@korsgaard.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