Re: [xmpp] dialback in DNA

Peter Saint-Andre - &yet <peter@andyet.net> Fri, 17 October 2014 02:30 UTC

Return-Path: <peter@andyet.net>
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 9E0C31A9028 for <xmpp@ietfa.amsl.com>; Thu, 16 Oct 2014 19:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_26=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 ejWA9VtvAVyn for <xmpp@ietfa.amsl.com>; Thu, 16 Oct 2014 19:30:46 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 116B41A1BA4 for <xmpp@ietf.org>; Thu, 16 Oct 2014 19:30:27 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id rl12so4773318iec.3 for <xmpp@ietf.org>; Thu, 16 Oct 2014 19:30:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Luc3jBklgYRM2fuq6WiWJULoCUepgGyDYzNhpgQGEEk=; b=jXNjZ0TFco/sqExtyn10sXARCYvHCBR04KRn1MGaRFlKBkeghtImbI2hdlqQNY9PgV L4j8Rp/bwvTqqBLgoAAgAhazBino2NkV8j1Ao8bB9is0ddsW8wC8/ZLHs9Rw6LIFzdWf 4AI/Cpn28vRGt7FhJFgiMGdtGHvk8RhJ1DLl75HREiNgpcg+NfCZOPgwN7U/xm3D8M0t OQoI1U3CsIRXdT3bETSXmVug1lX/A3lGOojaslEcHUpWi1UdiBql5tzb5RTIvXpmecAf rS24WJHgWJwKagAv6ZPk6M4PJ9CqwI0zld99XnbpBoTjXOzBb9yynFwY14nCCXtPK5iu rGtg==
X-Gm-Message-State: ALoCoQnsSi/VaQMh5VRmj3NiNh0pa0mXtK2p/CJyEBjcsWL9u+Y1QBDPGgUl1PdxliEi/1P1lRfC
X-Received: by 10.50.6.100 with SMTP id z4mr9162399igz.37.1413513023174; Thu, 16 Oct 2014 19:30:23 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id h8sm4042176ioh.35.2014.10.16.19.30.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 Oct 2014 19:30:22 -0700 (PDT)
Message-ID: <54407F3D.7060401@andyet.net>
Date: Thu, 16 Oct 2014 20:30:21 -0600
From: Peter Saint-Andre - &yet <peter@andyet.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Philipp Hancke <fippo@goodadvice.pages.de>, xmpp@ietf.org
References: <543BE0B7.3010609@andyet.net> <543C57DB.7040005@goodadvice.pages.de> <543D60B3.1020203@andyet.net> <544017A0.3000302@goodadvice.pages.de>
In-Reply-To: <544017A0.3000302@goodadvice.pages.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/Fa9Cu9JjBT-LRlPN0yCZ-1Fc_3k
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: Fri, 17 Oct 2014 02:30:47 -0000

On 10/16/14, 1:08 PM, Philipp Hancke wrote:
>> I'd need to double-check XEP-0220, one of our favorite documents. ;-)
>>
>>>>     an updated version of [XEP-0220], might define a DNA prooftype for
>>>>     dialback
>>>
>>> I just tried that and failed.
>>
>> How so?
>
> I could not figure out which proof of identity I wanted.
>
> Did I want the proof that the receiving server is who it claims to be?
> With dialback, the proof seems to be "oh yeah, it is listening on the
> port DNS says"? That's pretty bad but we know it is vulnerable to DNS
> poisoning...
>
> For the sending server, the proof is slightly better, db:verify and
> merlins spell assert the sender shares a secret with the authoritative
> server.

Thanks for the clarification.

> I just need to write up the formal prooftype definition for both.
>
> It seems this is more complicated for dialback than for PKIX or
> POSH/DANE because it's not symmetric there. OTOH, we might have
> scenarios where we have PKIX in one direction and POSH in the other.

True, that's possible. These things get messy. I think one way around 
the messiness is to say that DNA applies only to a single stream in a 
single direction. Bidi is interesting but what matters for DNA is that I 
check my server or peer.

Peter

-- 
Peter Saint-Andre
https://andyet.com/