From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Matthew Weber <matthew.weber@rockwellcollins.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/asterisk: security bump to version 16.21.1
Date: Sun, 24 Oct 2021 16:15:41 +0200 [thread overview]
Message-ID: <20211024161541.3258ff38@windsurf> (raw)
In-Reply-To: <20211021064029.31168-1-peter@korsgaard.com>
Hello Peter,
On Thu, 21 Oct 2021 08:40:28 +0200
Peter Korsgaard <peter@korsgaard.com> wrote:
> Fixes the following security issues:
I have applied to master, but what's quite worrying is that there were
0 CVEs affecting asterisk in version 16.14.1 according to
http://autobuild.buildroot.net/stats/master.html. Does this mean that
the Asterisk community is not submitting CVEs for their security
vulnerabilities ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-24 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 6:40 [Buildroot] [PATCH] package/asterisk: security bump to version 16.21.1 Peter Korsgaard
2021-10-24 14:15 ` Thomas Petazzoni [this message]
2021-10-24 15:09 ` Peter Korsgaard
2021-10-24 15:20 ` Peter Korsgaard
2021-10-24 21:10 ` Fabrice Fontaine
2021-10-25 7:20 ` Thomas Petazzoni
2021-10-25 13:59 ` [Buildroot] [External] " Weber, Matthew L Collins via buildroot
2021-10-26 12:28 ` [Buildroot] " Peter Korsgaard
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=20211024161541.3258ff38@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=matthew.weber@rockwellcollins.com \
--cc=peter@korsgaard.com \
--cc=yann.morin.1998@free.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.