From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Building AbiWord without libwmf and removing libwmf from Guix
Date: Sat, 27 May 2017 15:41:41 -0400 [thread overview]
Message-ID: <87tw46140a.fsf@netris.org> (raw)
In-Reply-To: <20170527170600.GA16269@jasmine> (Leo Famulari's message of "Sat, 27 May 2017 13:06:00 -0400")
Leo Famulari <leo@famulari.name> writes:
> The last update to libwmf was twelve years ago, in 2005. In the
> meantime, a large number of security issues have been discovered in this
> library. These bugs are fixed somewhat haphazardly by the distributions.
>
> While working on patching CVE-2016-9011 in libwmf, and backporting fixes
> for CVE-2016-{9317,10167,10168} in the ancient bundled libgd, I find
> myself wondering if we need this library at all. The patches from this
> 12 year span of 3rd party fixes begin to conflict with each other...
>
> Libwmf is only used as a "plugin" by AbiWord, and AbiWord can be
> configured to build without it.
What functionality would be lost? I guess that AbiWord would lose the
ability to open some kinds of files, but it would be good to know
whether or not such files are still in common use.
Mark
next prev parent reply other threads:[~2017-05-27 19:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 17:06 Building AbiWord without libwmf and removing libwmf from Guix Leo Famulari
2017-05-27 19:41 ` Mark H Weaver [this message]
2017-05-27 21:13 ` Ricardo Wurmus
2017-05-28 13:06 ` Hartmut Goebel
2017-05-28 18:44 ` Leo Famulari
2017-05-28 20:57 ` Ludovic Courtès
2017-06-23 22:30 ` Leo Famulari
2017-06-24 8:12 ` ng0
2017-06-24 8:02 ` ng0
2017-06-24 16:21 ` Leo Famulari
2017-06-24 22:52 ` Mark H Weaver
2017-06-25 3:37 ` Leo Famulari
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=87tw46140a.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.