Re: [xmpp] dialback in DNA

Philipp Hancke <fippo@goodadvice.pages.de> Mon, 13 October 2014 22:53 UTC

Return-Path: <fippo@goodadvice.pages.de>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76A1A1A1A34 for <xmpp@ietfa.amsl.com>; Mon, 13 Oct 2014 15:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level:
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_26=0.6, SPF_PASS=-0.001] autolearn=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 E60HY_Hx8e64 for <xmpp@ietfa.amsl.com>; Mon, 13 Oct 2014 15:53:22 -0700 (PDT)
Received: from lo.psyced.org (lost.IN.psyced.org [188.40.42.221]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 805291A0386 for <xmpp@ietf.org>; Mon, 13 Oct 2014 15:53:22 -0700 (PDT)
Received: from [192.168.178.45] (p5DCFDD14.dip0.t-ipconnect.de [93.207.221.20]) (authenticated bits=0) by lo.psyced.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id s9DMrXUC003663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <xmpp@ietf.org>; Tue, 14 Oct 2014 00:53:35 +0200
Message-ID: <543C57DB.7040005@goodadvice.pages.de>
Date: Tue, 14 Oct 2014 00:53:15 +0200
From: Philipp Hancke <fippo@goodadvice.pages.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: xmpp@ietf.org
References: <543BE0B7.3010609@andyet.net>
In-Reply-To: <543BE0B7.3010609@andyet.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/VKF5F3EdRRK9CX0kZUMQ-eI41vo
Subject: Re: [xmpp] dialback in DNA
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Oct 2014 22:53:25 -0000

Am 13.10.2014 16:24, schrieb Peter Saint-Andre - &yet:
[...]
> Matt and I propose adding the following text to ยง7:
>
>     Although the PKIX prooftype uses the XMPP Server Dialback protocol

reuses?

>     [XEP-0220] for signalling between servers, this framework document

[XEP-0220] _syntax_ for ...?

>     does not define the exchange of dialback keys (also specified in
>     [XEP-0220]) as a DNA prooftype.  However, a future specification, or

but doesn't use the semantics for the generation and validation of 
dialback keys?

I'd note that it will still work with server dialback because one of the 
design goals was backward compat. So we don't need to define anything.

>     an updated version of [XEP-0220], might define a DNA prooftype for
>     dialback

I just tried that and failed. Let's try to find some time and a 
whiteboard later this year.

> in a way that is consistent with this framework.

0220 currently says that dialback-without-dialing-back is not described. 
smart servers should not use the db:verify to do any weak identify 
verification of the dialback keys.
But if we make any such statements, they belong into the security 
considerations of xep-0220.