From: Tim Waugh <twaugh@redhat.com>
To: Koji Otani <sho@bbr.jp>
Cc: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] XPdf bundling in pdftoopvp as well
Date: Wed, 07 Mar 2012 09:50:27 +0000 [thread overview]
Message-ID: <1331113827.3119.7.camel@rubik> (raw)
In-Reply-To: <20120306.144653.295962394.sho@bbr.jp>
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
On Tue, 2012-03-06 at 14:46 +0900, Koji Otani wrote:
> oprs/*Splash*.cxx are not copied from poppler while they use poppler data.
> There may have vulnerabilities, but it's not because of copying from
> poppler. We should fix them in pdftoopvp.
OK, that's good. I haven't audited them so I don't know whether they
have any security issues. I just want to make sure that duplication
from xpdf/poppler is kept to a minimum, or even avoided entirely.
Tim.
*/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
prev parent reply other threads:[~2012-03-07 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 12:04 [Printing-architecture] XPdf bundling in pdftoopvp as well Tim Waugh
2012-03-02 12:12 ` Till Kamppeter
2012-03-02 12:38 ` Koji Otani
2012-03-05 12:09 ` Tim Waugh
2012-03-06 5:46 ` Koji Otani
2012-03-07 9:50 ` Tim Waugh [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=1331113827.3119.7.camel@rubik \
--to=twaugh@redhat.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=sho@bbr.jp \
/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.