From: rdkehn at yahoo.com <rdkehn@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH v2 0/4] package/dhcp
Date: Wed, 13 Jan 2016 16:38:27 -0600 [thread overview]
Message-ID: <20160113223827.GA14232@dkarchlinux64.currentcomm.com> (raw)
In-Reply-To: <5696c2e46d700_16baf34c4c4499@ultri2.mail>
Hi Richardo,
On Wed, Jan 13, 2016 at 07:34:28PM -0200, Ricardo Martincoski wrote:
> Hi Doug,
>
> On Sun, 10 Jan 2016 15:25:05 -0600, Doug Kehn wrote:
> > This patch series bumps dhcp package to 4.3.3. I'm doing this as an RFC to get
> [snip]
>
> There is a new release for isc-dhcp from yesterday. It's a security update.
>
> https://kb.isc.org/article/AA-01334/0/CVE-2015-8605%3A-UDP-payload-length-not-properly-checked.html
> DHCP version 4.1-ESV-R12-P1
> DHCP version 4.3.3-P1
>
> IMO we should have a new version of the patch series before committing it.
Agree, thanks.
Does the series need to retain the RFC tag, or is the handling of
the embedded bind tar-ball acceptable?
Regards,
...doug
next prev parent reply other threads:[~2016-01-13 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 21:34 [Buildroot] [RFC PATCH v2 0/4] package/dhcp Ricardo Martincoski
2016-01-13 22:38 ` rdkehn at yahoo.com [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-14 23:27 Ricardo Martincoski
2016-01-10 21:25 Doug Kehn
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=20160113223827.GA14232@dkarchlinux64.currentcomm.com \
--to=rdkehn@yahoo.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