Re: [stir] Permitted spoofing

Wilhelm Wimmreuter <wilhelm@wimmreuter.de> Tue, 11 June 2013 21:35 UTC

Return-Path: <wilhelm@wimmreuter.de>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BE3621F9967 for <stir@ietfa.amsl.com>; Tue, 11 Jun 2013 14:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tFOUGtt9VHp3 for <stir@ietfa.amsl.com>; Tue, 11 Jun 2013 14:35:16 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by ietfa.amsl.com (Postfix) with ESMTP id 6B7BA21F9977 for <stir@ietf.org>; Tue, 11 Jun 2013 14:35:16 -0700 (PDT)
Received: from wwnet.ww (p5DE95C29.dip0.t-ipconnect.de [93.233.92.41]) by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis) id 0M4a7A-1URWxT1J6a-00zDhr; Tue, 11 Jun 2013 23:35:15 +0200
Received: by wwnet.ww (Postfix, from userid 783) id 98B8F88BA2A; Tue, 11 Jun 2013 23:35:14 +0200 (CEST)
Received: from [192.168.178.24] (unknown [192.168.178.24]) (Authenticated sender: williw) by wwnet.ww (Postfix) with ESMTPSA id AA136888526; Tue, 11 Jun 2013 23:35:06 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="us-ascii"
From: Wilhelm Wimmreuter <wilhelm@wimmreuter.de>
In-Reply-To: <CDDD0303.1CE56%brian.rosen@neustar.biz>
Date: Tue, 11 Jun 2013 23:35:05 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <35573943-5A08-4CAB-AEA7-559B5F870F41@wimmreuter.de>
References: <CDDD0303.1CE56%brian.rosen@neustar.biz>
To: "Rosen, Brian" <Brian.Rosen@neustar.biz>
X-Mailer: Apple Mail (2.1085)
X-Provags-ID: V02:K0:rwXo99JXY/x+AZgqzOlpjr0gm0tFxLsmNm4WTeSfJ6o 84BXsWf/xRRCdHYJD2gMyp1YaexFiVrrrdn7FH0xm/J6qdEbBV m2/xQJVt/jnLXmHEL7tnf51jUthM3oaMtKbppfzoJdpXufpqZa RRlxgBw4N5Ijnzo18PiSCgsyjJ3i6StK+1zM8GNj/SrEMRN+J5 os3IC5ZA7XKST9t4VCQBiq0hnFJG+Kt9M+OU39kzwv8lkVw7K1 R259XE65fXnUw89ZxC6JRaKUpGYk7HAxGl7oFK6DMFPuhV8KHe y8GCgdmqVR54GDkR1DeUDDPBSJ/2jzdd7pCzs/TmLJ7K4zaoB4 OhxlpOuOdzwkO4HzMa8C6/hEb/zO1XHOdMHJs8GrJ
Cc: "hadriel.kaplan@oracle.com" <hadriel.kaplan@oracle.com>, Michael Hammer <michael.hammer@yaanatech.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "stir@ietf.org" <stir@ietf.org>, "hgs@cs.columbia.edu" <hgs@cs.columbia.edu>
Subject: Re: [stir] Permitted spoofing
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stir>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jun 2013 21:35:21 -0000

On 11.06.2013, at 22:41, Rosen, Brian wrote:

> This is not just MITM.
> 
> The bad guy just needs to receive any good call, and then use it to
> impersonate the person who called them.
> 
> I think we need the To, From, some form of call-id and a timestamp to get
> a decent signature.
Yes,
... confessed in my previous message already ;-)


> We don't have domains in this discussion - we have telephone numbers, so I
> think DANE can't help us.

 OK, but server authentication is definitely next.
DNS is the only way to reach these servers today. We are farther on the Internet than typical PSTN paradigms allow us to follow.

 SIP does not have decent server authentication and therefore one can pretend to be your telecom server of choice.

Willi

> 
> Brian
> 
> On 6/11/13 4:37 PM, "Wilhelm Wimmreuter" <wilhelm@wimmreuter.de> wrote:
> 
>> Guess this is MITM is the next VoIP issue to come up.
>> 
>> Both way authentication is not considered for VoIP because service
>> providers are trusted by default. ;-)
>> 
>> 
>> DANE WG with their DNSsec approach might be a solution for this MITM
>> issues as well?
>> 
>> 
>> BTWY:
>> We had nasty routing issues in pure PSTN as well. There the MITM could
>> pretend being a fixed network operator instead of a mobile operator to
>> "optimize" their business case on termination fees.
>> 
>> Willi
>> 
>> 
>> 
>> 
>> On 11.06.2013, at 18:12, Dave Crocker wrote:
>> 
>>> On 6/11/2013 6:03 AM, Rosen, Brian wrote:
>>>> MITM is a potential problem, which would be desirable to cut off, but
>>>> it's not the stated problem we're trying to solve.
>>>> 
>>>> There may be some number of service providers in the path that are
>>>> tolerant of the problem, but not really complicit.
>>> 
>>> 
>>> This could have a pretty substantial effect on design choices.
>>> 
>>> For example, session-based SSL authentication -- that is, without
>>> server validation (certs) -- permits MITM, which seems to be
>>> often/generally acceptable in terms of actual practice, although
>>> rhetoric claims otherwise.
>>> 
>>> But in general, I've had the impression that any effort at
>>> authentication or confidentiality comes with an expectation of
>>> resistance to MITM compromises.
>>> 
>>> d/
>>> 
>>> -- 
>>> Dave Crocker
>>> Brandenburg InternetWorking
>>> bbiw.net
>>> _______________________________________________
>>> stir mailing list
>>> stir@ietf.org
>>> https://www.ietf.org/mailman/listinfo/stir
>>> 
>> 
> 
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir
>