IETF Logo Mail Archive

Re: [Cbor] Failure Testcases

Richter, Jörg <Joerg.Richter@pdv-FS.de> Wed, 30 January 2019 21:15 UTC

Return-Path: <Joerg.Richter@pdv-FS.de>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D4C6130FF3 for <cbor@ietfa.amsl.com>; Wed, 30 Jan 2019 13:15:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 pIhQtIDXVDxf for <cbor@ietfa.amsl.com>; Wed, 30 Jan 2019 13:15:52 -0800 (PST)
Received: from mail.pdv-fs.de (mail.pdv-fs.de [213.208.220.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C643B130FEC for <cbor@ietf.org>; Wed, 30 Jan 2019 13:15:51 -0800 (PST)
Received: from EXCHDB1.pdv-fs.de (192.168.180.94) by EXCHDB2.pdv-fs.de (192.168.180.95) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Wed, 30 Jan 2019 22:15:50 +0100
Received: from EXCHDB1.pdv-fs.de ([fe80::6c4a:8b1b:60f4:4437]) by EXCHDB1.pdv-fs.de ([fe80::6c4a:8b1b:60f4:4437%15]) with mapi id 15.01.1466.012; Wed, 30 Jan 2019 22:15:50 +0100
From: "Richter, Jörg" <Joerg.Richter@pdv-FS.de>
To: "cbor@ietf.org" <cbor@ietf.org>
Thread-Topic: Failure Testcases
Thread-Index: AQHUuOD5MlGd7+ZyLUWirITWL4yp7Q==
Date: Wed, 30 Jan 2019 21:15:50 +0000
Message-ID: <aa92402418844ae2b16c70136f652b14@pdv-FS.de>
References: <3da886c762564d20a75796733ec73e23@pdv-FS.de>
In-Reply-To: <3da886c762564d20a75796733ec73e23@pdv-FS.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.185.1]
Content-Type: multipart/mixed; boundary="_003_aa92402418844ae2b16c70136f652b14pdvFSde_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/kNxYM7Jw3uJQ2MvyGU0Jlqhw9Vw>
Subject: Re: [Cbor] Failure Testcases
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2019 21:15:55 -0000

I had of course some mistakes in my script. Attached is the fixed 
version with now only 568 test cases.
Every other single- and two-byte message should fail with 
"end of message" or should succeed with decoding.

Note that it is important to differentiate the failures into 
"end of message" and something else. The attached list 
contains only the other failures.

I am fairly sure that most, if not all, possible decoder problems 
for invalid CBOR should be found with this list. CBOR is so simple, 
that all possible problems can be triggered with the first two 
bytes of an element. 
This does not apply to decoders that, for example, run through 
different code paths for map elements than for the root element. 
But a straight forward recursive decoder would use the same code path.

- Jörg

v2.23.0 | Report a Bug | By Email