public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Cc: "Dr. Volker Zell" <dr.volker.zell@oracle.com>
Subject: Re: [SECURITY] libwmf
Date: Thu, 09 Jul 2015 20:09:00 -0000	[thread overview]
Message-ID: <1436472549.7208.46.camel@cygwin.com> (raw)
In-Reply-To: <vriv381a33vq.fsf@VZELL-LAP.de.oracle.com>

On Mon, 2015-06-29 at 17:56 +0200, Dr. Volker Zell wrote:
> >>>>> Yaakov Selkowitz writes:
>     > On Mon, 2015-06-08 at 15:42 -0500, Yaakov Selkowitz wrote:
>     >> On Fri, 2015-06-05 at 03:17 -0500, Yaakov Selkowitz wrote:
>     >> > Dr. Volker,
>     >> > 
>     >> > A security vulnerability has been made public for libwmf:
>     >> > 
>     >> > https://bugzilla.redhat.com/show_bug.cgi?id=1227243
>     >> 
>     >> Actually, it's worse than that.  Despite configuring with --with-sys-gd,
>     >> libwmf is still being built with the bundled libgd (which has either an
>     >> older or custom API) instead of the system one.  Therefore, practically
>     >> the entire patchset is required to fix all known vulnerabilities:
>     >> 
>     >> http://pkgs.fedoraproject.org/cgit/libwmf.git/
> 
>     > Are you still with us?  
> 
> Yes, but NO time right now (plus upcoming vacation)

Understood, I've uploaded 0.2.8.4-15 with the complete patchset.

BTW, tzcode has been a bit neglected as of late, and it's the sort of
package that really needs to be kept timely (forgive the pun).  Would
you mind if we took over maintainership?

--
Yaakov


  reply	other threads:[~2015-07-09 20:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05  8:17 Yaakov Selkowitz
2015-06-08 20:42 ` Yaakov Selkowitz
2015-06-26 16:51   ` Yaakov Selkowitz
2015-06-29 15:56     ` Dr. Volker Zell
2015-07-09 20:09       ` Yaakov Selkowitz [this message]
2015-07-10  5:43         ` Dr. Volker Zell

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=1436472549.7208.46.camel@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    --cc=dr.volker.zell@oracle.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).