[Rum] How to do the impossible: MITMs that aren't but are

Eric Burger <eburger@standardstrack.com> Wed, 27 March 2019 15:04 UTC

Return-Path: <eburger@standardstrack.com>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2675F1202D6 for <rum@ietfa.amsl.com>; Wed, 27 Mar 2019 08:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.69
X-Spam-Level:
X-Spam-Status: No, score=-1.69 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=standardstrack.com
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 mQ6huLofaRIG for <rum@ietfa.amsl.com>; Wed, 27 Mar 2019 08:04:43 -0700 (PDT)
Received: from biz221.inmotionhosting.com (biz221.inmotionhosting.com [198.46.93.79]) (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 EC37B1202DB for <rum@ietf.org>; Wed, 27 Mar 2019 08:04:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=standardstrack.com; s=default; h=To:Date:Message-Id:Subject:Mime-Version: Content-Type:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=IJA0cyLI754Y7iJrEaSRfSdpoome4r4T5DCwekSpoE0=; b=g1d8ZJaZlH6wsn+M6dUCaLKrjW M2gc4yMwJf2gPZ93EHrbo9MLKfohpWhQDuuELtEYRpp3coW4fBWukQ0C4UucNKffI3x/STykMqwOM M7ZCZua9PQtFqxSqiEFw61IIQPuQPp3U85ebDw/uP817XzqJOm6kHjdeWyUZ1dQ2gK58=;
Received: from [174.204.14.136] (port=2527 helo=[192.168.43.104]) by biz221.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <eburger@standardstrack.com>) id 1h9A6U-0000wP-GJ for rum@ietf.org; Wed, 27 Mar 2019 08:04:42 -0700
From: Eric Burger <eburger@standardstrack.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_541E1035-47F5-4B7A-8DAC-023EB0FD94B9"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Message-Id: <AC121920-E46F-4691-8A10-F4D2A412B3C2@standardstrack.com>
Date: Wed, 27 Mar 2019 11:04:32 -0400
To: rum@ietf.org
X-Mailer: Apple Mail (2.3445.104.8)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz221.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz221.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Authenticated-Sender: biz221.inmotionhosting.com: eburger@standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/9PJXVyn2UiakTOYIobJaMcFY4NQ>
Subject: [Rum] How to do the impossible: MITMs that aren't but are
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2019 15:04:44 -0000

In DISPATCH it was pointed out that RUM is a man-in-the-middle (MITM) attack. We pointed out that it is a MITM that users expect.

The good news is we have existing use cases that look a lot like the RUM scenario: a PBX re-originating a call and a multimedia conference bridge. However, neither of those scenarios have end-to-end, cryptographic integrity of the identity of the end parties to each other.

I would offer that we have non-protocol solutions to this problem that could be enabled through the protocol.

How about this as an outline:
o   Note the originating party can pass an opaque token to the Interpreter to pass to the called party (e.g., a STIR token)

o   Note the Interpreter can pass that token to the called party (noting that STIR tokens are somewhat cut-and-paste attack resistant)

o   Note that in many jurisdictions, communications regulators have authority over Interpreters to ensure they act responsibly

o   Note that in many jurisdictions, communications regulators impose mechanisms that apply cryptographic tools so that a called party knows the Interpreter is really a ‘legal’ (in the legal sense) Interpreter (e.g., SHAKEN)

Would that work? Otherwise, I think we are trying to solve an unsolvable problem: specifically a MITM that knows when to set the Evil Bit.