Re: [DNSOP] proposal: Covert in-band zone data

Witold Krecicki <wpk@isc.org> Fri, 02 August 2019 14:46 UTC

Return-Path: <wpk@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37E4112033A for <dnsop@ietfa.amsl.com>; Fri, 2 Aug 2019 07:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-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 tdap1Nnq0JVN for <dnsop@ietfa.amsl.com>; Fri, 2 Aug 2019 07:46:35 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 DC9A2120336 for <dnsop@ietf.org>; Fri, 2 Aug 2019 07:46:35 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id B1E7B3AB000; Fri, 2 Aug 2019 14:46:34 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 97483160055; Fri, 2 Aug 2019 14:46:34 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 6FAAE16008C; Fri, 2 Aug 2019 14:46:34 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ZJEaArEWoaUR; Fri, 2 Aug 2019 14:46:34 +0000 (UTC)
Received: from [192.168.69.142] (unknown [31.179.189.14]) by zmx1.isc.org (Postfix) with ESMTPSA id DE1B2160055; Fri, 2 Aug 2019 14:46:32 +0000 (UTC)
To: Paul Ebersman <list-dnsop@dragon.net>
Cc: dnsop@ietf.org
References: <20190706213024.GA56650@isc.org> <alpine.BSF.2.21.9999.1907221704030.7062@bikeshed.isc.org> <CAN6NTqymm6+OMet0sMZC0Ms5E_5mj_nwONk3fR19HwgWXYNB4Q@mail.gmail.com> <alpine.LRH.2.21.1907251332070.10708@bofh.nohats.ca> <20190725183051.33DA315BFD9D@fafnir.remote.dragon.net> <alpine.BSF.2.21.9999.1907301916050.7062@bikeshed.isc.org> <20190730200859.A424215E6AD4@fafnir.remote.dragon.net> <alpine.BSF.2.21.9999.1907302009500.7062@bikeshed.isc.org> <20190730201628.1496015E6BFA@fafnir.remote.dragon.net> <2b2a0e4d-3720-b88c-6377-195117896e8f@isc.org> <20190802143247.A9E251601056@fafnir.remote.dragon.net>
From: Witold Krecicki <wpk@isc.org>
Message-ID: <91c0669e-66b5-05d6-d788-59aea804a13e@isc.org>
Date: Fri, 02 Aug 2019 16:46:29 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <20190802143247.A9E251601056@fafnir.remote.dragon.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/pYL4TpRuTXu2trCyeMuUaVhvJVo>
Subject: Re: [DNSOP] proposal: Covert in-band zone data
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2019 14:46:37 -0000

W dniu 02.08.2019 o 16:32, Paul Ebersman pisze:
> ebersman> If what you're arguing for is something that's actually mixed
> ebersman> into the zone data, how do you handle non-compatible/legacy
> ebersman> and avoid leakage?
> 
> wpk> non-compatible/legacy servers won't know the RRTypes that are
> wpk> covert - and therefore won't be able to load them from disk.
> 
> In a polite/sane implementation, sure. But I have scars from my years at
> ISC tech support dealing with very broken implementations not done by
> the usual FOSS DNS folks. They might fail to load the zone at all, might
> stop loading and serve what they have, only serve what they recognize,
> crash, etc.
They should fail to load the zone as it will contain RRs that it does
not understand. As long as they won't serve covert records to general
public - I don't really care.

Witold