From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: mupdf: Fix some security problems in bundled mujs.
Date: Thu, 12 Jan 2017 20:46:52 +0100 [thread overview]
Message-ID: <87wpe05adv.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170112183017.GB23706@jasmine>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Leo Famulari <leo@famulari.name> writes:
> Can you include links to the upstream bug reports in the patch files?
Good catch; added.
> Through cups, this requires ~600 rebuilds. I wonder if we can graft it?
> That is, is the ABI compatible?
Good question. The null pointer dereference patch renames a function,
and I can find it in /gnu/store/...-mupdf-1.10a/lib/libmupdfthird.a. So
I guess not.
There is also /lib/libmupdf.a which I assume most packages use, and does
not seem to use anything from mujs.
This package only provides static libraries, so grafting may not even
work. In most cases I've come across, the static library is embedded
with "ar" in the final package (cups do not retain a rerefence to
mupdf). What to do?
(as an aside, I wonder if we can add an "ar-wrapper" that creates thin
archives by default).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-01-12 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 18:06 [PATCH] gnu: mupdf: Fix some security problems in bundled mujs Marius Bakke
2017-01-12 18:30 ` Leo Famulari
2017-01-12 19:46 ` Marius Bakke [this message]
2017-01-12 20:03 ` Leo Famulari
2017-01-13 0:59 ` Mark H Weaver
2017-01-13 17:34 ` Leo Famulari
2017-01-15 8:20 ` Mark H Weaver
2017-01-15 18:47 ` Leo Famulari
2017-01-15 19:05 ` Marius Bakke
2017-01-15 20:49 ` Leo Famulari
2017-01-15 20:56 ` Marius Bakke
2017-01-15 23:05 ` Mark H Weaver
2017-01-16 1:27 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpe05adv.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).