From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V2 1/1] ntp: security bump to verserion 4.2.8p9
Date: Tue, 7 Nov 2017 18:26:20 +0100 [thread overview]
Message-ID: <20171107182620.3c8df7ff@windsurf> (raw)
In-Reply-To: <20170206141225.2311-1-aduskett@codeblue.com>
Hello,
On Mon, 6 Feb 2017 09:12:25 -0500, Adam Duskett wrote:
> This version of ntp fixes several vulnerabilities.
>
> CVE-2016-9311
> CVE-2016-9310
> CVE-2016-7427
> CVE-2016-7428
> CVE-2016-9312
> CVE-2016-7431
> CVE-2016-7434
> CVE-2016-7429
> CVE-2016-7426
> CVE-2016-7433
>
> http://www.kb.cert.org/vuls/id/633847
>
> In addition, libssl_compat.h is now included in many files, which
> references openssl/evp.h, openssl/dsa.h, and openssl/rsa.h.
> Even if a you pass --disable-ssl as a configuration option, these
> files are now required.
>
> As such, I have also added openssl as a dependency, and it is now
> automatically selected when you select ntp.
>
> Signed-off-by: Adam Duskett <aduskett@codeblue.com>
This patch raised a comment on Github:
https://github.com/buildroot/buildroot/commit/ebf6f64b76059e31a85f982cb04f80ad5982dac3#commitcomment-25458671.
Apparently, building without OpenSSL is still possible (perhaps has
been fixed in 4.2.8p10 ?), and some users would like ntp without
OpenSSL support.
Adam, could you have a look into this ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-07 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 14:12 [Buildroot] [V2 1/1] ntp: security bump to verserion 4.2.8p9 Adam Duskett
2017-02-06 14:58 ` Thomas Petazzoni
[not found] ` <1486393216.2005.19.camel@codeblue.com>
2017-02-06 15:02 ` Thomas Petazzoni
2017-02-06 15:23 ` Arnout Vandecappelle
2017-02-06 21:18 ` Adam Duskett
2017-02-07 14:28 ` Peter Korsgaard
2017-02-07 14:29 ` Peter Korsgaard
2017-11-07 17:26 ` Thomas Petazzoni [this message]
2017-11-07 21:15 ` Adam Duskett
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=20171107182620.3c8df7ff@windsurf \
--to=thomas.petazzoni@free-electrons.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 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.