From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by yquem.inria.fr (Postfix) with ESMTP id 637C4BC37 for ; Fri, 16 Oct 2009 18:01:06 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: At4DACM12EpQRFuwWWdsb2JhbACbDAEUF74IhDAE X-IronPort-AV: E=Sophos;i="4.44,574,1249250400"; d="scan'208";a="35071045" Received: from furbychan.cocan.org ([80.68.91.176]) by mail2-smtp-roc.national.inria.fr with ESMTP; 16 Oct 2009 18:01:06 +0200 Received: from rich by furbychan.cocan.org with local (Exim 4.63) (envelope-from ) id 1MypEn-0007O7-E1; Fri, 16 Oct 2009 17:01:05 +0100 Date: Fri, 16 Oct 2009 17:01:05 +0100 To: Jun Furuse Cc: caml-list@inria.fr, Anil Madhavapeddy Subject: Re: [Caml-list] Camlimages integer overflows with PNG images Message-ID: <20091016160105.GA7469@annexia.org> References: <20090703113838.GA8086@annexia.org> <0D39970B-7727-4503-A218-C8CDD3B64F4D@recoil.org> <20090703172803.GA22720@annexia.org> <0554DF81-B2CD-4B0A-8988-C6627594CB0B@recoil.org> <20090703183507.GA26539@annexia.org> <5160b4200907031856g247ebbe9va973b9447572e4e6@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5160b4200907031856g247ebbe9va973b9447572e4e6@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) From: Richard Jones X-Spam: no; 0.00; camlimages:01 furuse:01 camlimages:01 cvs:01 cvs:01 intending:01 2009:98 wrote:01 overflows:01 integer:01 caml-list:01 upstream:04 jul:05 images:93 red:92 On Sat, Jul 04, 2009 at 10:56:50AM +0900, Jun Furuse wrote: > Coincidentally I am working on png reading code of camlimages again this week. > I will check the patch and incorporate it to the CVS version soon. I'm not sure if we can get to the CVS version of camlimages? Anyhow, after a series of problems I'm intending to drop camlimages from Fedora ... unless you can assure me that an upstream release which comprehensively fixes the problems is going to appear soon. Rich. -- Richard Jones Red Hat