From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libbsd: security bump to version 0.10.0
Date: Mon, 12 Aug 2019 23:04:35 +0200 [thread overview]
Message-ID: <20190812230435.3af62777@windsurf.home> (raw)
In-Reply-To: <20190812163744.10101-1-fontaine.fabrice@gmail.com>
On Mon, 12 Aug 2019 18:37:44 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> - Remove patch (already in version)
> - Update site to get the latest version
> - Update hash of license file (update in year, new file and author)
> - Remove !(BR2_TOOLCHAIN_USES_UCLIBC && !BR2_USE_MMU) dependency,
> __register_at_fork availability is correclty checked since
> https://gitlab.freedesktop.org/libbsd/libbsd/commit/b0ebb0d4c26b281facbab7a774510b541637b13b
> - Includes Several security related fixes for nlist() reported by Daniel
> Hodson and one by Coverity Scan, see
> https://lists.freedesktop.org/archives/libbsd/2019-August/000229.html
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/fwts/Config.in | 2 +-
> ...0001-flopen-fix-build-with-musl-libc.patch | 40 -------------------
> package/libbsd/Config.in | 2 -
> package/libbsd/libbsd.hash | 6 +--
> package/libbsd/libbsd.mk | 4 +-
> 5 files changed, 6 insertions(+), 48 deletions(-)
> delete mode 100644 package/libbsd/0001-flopen-fix-build-with-musl-libc.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-12 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 16:37 [Buildroot] [PATCH 1/1] package/libbsd: security bump to version 0.10.0 Fabrice Fontaine
2019-08-12 17:19 ` Yann E. MORIN
2019-08-12 21:04 ` Thomas Petazzoni [this message]
2019-09-02 11:53 ` 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=20190812230435.3af62777@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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