All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] quagga: security bump to version 1.0.20160309
Date: Wed, 16 Mar 2016 10:23:32 +0200	[thread overview]
Message-ID: <20160316082332.GR5528@tarshish> (raw)
In-Reply-To: <87mvpy6dg0.fsf@dell.be.48ers.dk>

Hi Peter,

On Wed, Mar 16, 2016 at 09:21:03AM +0100, Peter Korsgaard wrote:
> >>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> 
>  > Fixes CVE-2016-2342 (AKA VU#270232): Quagga bgpd with BGP peers enabled for
>  > VPNv4 contains a buffer overflow vulnerability.
> 
>  > Remove the --enable-babeld and --enable-opaque-lsa configure options that were
>  > removed in this release.
> 
>  > See the release announcement at
>  > https://lists.quagga.net/pipermail/quagga-dev/2016-March/014938.html.
> 
> This unfortunately causes some new build errors:
> 
> http://autobuild.buildroot.net/?reason=quagga-1.0.20160309
> 
> make[3]: *** No rule to make target `../ospfd/libospf.la', needed by `libospfapiclient.la'.  Stop.
> 
> Perhaps a parallel build issue? Care to take a look?

I noticed that. I'll look into it later today.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      reply	other threads:[~2016-03-16  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 16:12 [Buildroot] [PATCH] quagga: security bump to version 1.0.20160309 Baruch Siach
2016-03-15 19:56 ` Peter Korsgaard
2016-03-16  8:21 ` Peter Korsgaard
2016-03-16  8:23   ` Baruch Siach [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=20160316082332.GR5528@tarshish \
    --to=baruch@tkos.co.il \
    --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.