From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <1330600735.18587.3.camel@rubik> From: Tim Waugh Date: Thu, 01 Mar 2012 11:18:55 +0000 Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-9m29Quo9vo++NZhoF7xk" Mime-Version: 1.0 Subject: [Printing-architecture] pdftopdf List-Id: Printing architecture under linux List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Till Kamppeter Cc: Open Printing --=-9m29Quo9vo++NZhoF7xk Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Looking at the source code to pdftopdf, it seems like it is *another* fork of xpdf. Is there a reason it can't use the poppler library to do what it needs to do? Has it been security audited, or at least have the recent xpdf vulnerabilities from the last few years been verified not to be present in pdftopdf? Thanks, Tim. */ --=-9m29Quo9vo++NZhoF7xk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQEVAwUAT09bH+7Fkar03pQsAQLMYwgAneXqrzILtm17/M+R4+9aIaQEfcp5jvN3 OB3EfxOu3Obk3Y2jUj9rId+y2VLCqntChjCL3dIH3AbHJeYydEMWW6Wwob8oxt+I ky2riIrlMSXxpwyjXm9nSgIq5/xAdD6D7yiWhmJ0ciEja1KjAbw04krih3GsJ2KN JjHcx/26JLv0sGAdhbWubGP8vH9vusi5Ei4i4v9XDvcVRhKeezyPCVw9G8xuBmKr JX9AtQ7macMwVDh/gqNvlNv054vCxS9t77zsdePUuWZQOnA1iH6/1DSXlfDl0s2+ /6WNeqvYI3bWFI6zSToG1O6s0ml2lHNr+ZQOc1Oy184eGScz4WpR/w== =Pu1K -----END PGP SIGNATURE----- --=-9m29Quo9vo++NZhoF7xk--