Re: [Tools-discuss] RFC PDF crashes viewer

Erik Auerswald <auerswal@unix-ag.uni-kl.de> Mon, 29 June 2020 18:19 UTC

Return-Path: <auerswal@unix-ag.uni-kl.de>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED63C3A0942 for <tools-discuss@ietfa.amsl.com>; Mon, 29 Jun 2020 11:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAY_BE_FORGED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WvJ_7K1YpvpQ for <tools-discuss@ietfa.amsl.com>; Mon, 29 Jun 2020 11:19:15 -0700 (PDT)
Received: from mailgw1.uni-kl.de (mailgw1.uni-kl.de [IPv6:2001:638:208:120::220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5AC53A093C for <tools-discuss@ietf.org>; Mon, 29 Jun 2020 11:19:14 -0700 (PDT)
Received: from [172.20.10.2] (x2e720048.dyn.telefonica.de [46.114.0.72] (may be forged)) (authenticated bits=0) by mailgw1.uni-kl.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 05TIHgMn022057 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tools-discuss@ietf.org>; Mon, 29 Jun 2020 20:19:01 +0200
To: tools-discuss@ietf.org
References: <0DE4B90E-B03A-45BB-959B-89B695217188@tzi.org> <2DE9781A-E192-4E9C-838C-B7D67B1D4256@vigilsec.com> <20200626203214.GA16307@unix-ag.uni-kl.de>
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Message-ID: <3385823f-b484-ad6f-f780-c581edd1b2fe@unix-ag.uni-kl.de>
Date: Mon, 29 Jun 2020 20:17:39 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <20200626203214.GA16307@unix-ag.uni-kl.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/12Efvwr7KXrgjVTWpaR4pa2hv-U>
Subject: Re: [Tools-discuss] RFC PDF crashes viewer
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2020 18:19:17 -0000

Hi all,

as another data point, the AUTH48 versions of the PDF rendering of
RFC 8792 worked fine in evince.  Viewing them in MuPDF did not produce
any error or warning messages.

The published version of the PDF does crash evince, and produce error
and warning messages (as below) in MuPDF.

As an obvious difference between the two files, the published PDF
embeds the XML version of the RFC, while the AUTH48 versions did not.

Thanks,
Erik

On 26.06.20 22:32, Erik Auerswald wrote:
> Hi,
> 
> while MuPDF can open and display the file, it produces many instances of
> two  messages (one error, one warning):
> 
>      $ mupdf rfc8798.pdf
>      error: Unable to read ICC workflow
>      warning: Attempt to read Output Intent failed
>      [...]
> 
> For every page, a new burst of several instances of the above two messages
> is printed.
> 
> Firefox displays the PDF file.
> 
> The GNOME Document Viewer (evince) crashes.
> 
> There are other PDF renderings of RFCs that crash evince, e.g., RFCs 8651
> to 8655.  Those produce the same messages with MuPDF as RFC 8798, but MuPDF
> does display them.  Both Firefox's and Chrome's built-in PDF viewers can
> display those PDF renderings of RFCs.
> 
> I agree with Carsten that this is a bug in evince, but evince works fine
> for most PDF files out there, including many that Firefox cannot display
> correctly.  Since MuPDF produces error and warning messages, and evince
> crashes, it seems to me as if it were likely that the PDF versions of
> recent RFCs do have issues.
> 
> Thanks,
> Erik
> 
> On Fri, Jun 26, 2020 at 02:02:20PM -0400, Russ Housley wrote:
>> I just opened that file with three different viewers.  They all worked.
>>
>> Russ
>>
>>
>>> On Jun 26, 2020, at 11:44 AM, Carsten Bormann <cabo@tzi.org> wrote:
>>>
>>> This is undoubtedly a bug in the viewer, but I have received a report the PDF viewer evince (tested with versions 3.30.2 and 3.36.5, i.e., newer than CVE-2019-1010006) crashes when trying to view:
>>>
>>> https://www.rfc-editor.org/rfc/rfc8798.pdf
>>>
>>> I have no further data at this time.
>>>
>>> Grüße, Carsten