Re: [rtcweb] Fwd: New Version Notification for draft-uberti-rtcweb-turn-rest-00.txt

Martin Thomson <> Mon, 08 July 2013 21:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4A9F321F9E45 for <>; Mon, 8 Jul 2013 14:43:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.844
X-Spam-Status: No, score=-1.844 tagged_above=-999 required=5 tests=[AWL=-0.484, BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_LWSHORTT=1.24]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8pJExh0ozfPT for <>; Mon, 8 Jul 2013 14:43:37 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c05::22c]) by (Postfix) with ESMTP id 7BA2C21F9E24 for <>; Mon, 8 Jul 2013 14:43:37 -0700 (PDT)
Received: by with SMTP id c10so9500504wiw.5 for <>; Mon, 08 Jul 2013 14:43:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=O3ht9iEuPelweko45dtCDtZLQmLuVhebDiONY+bpFuU=; b=NT6YsrDQzoKfocnHrYhV7clrBs8GbDZmTg6Hsf88Gz9wBXbHRP2b1a+g3+a4Z6OviL 5+P4kMP96yn/ygXQlt/QIt+tqeJISJko/HGgojbzKdbA8lejt8HXnLiBiwc8iOqKe3oO gorAxEEW737OpJhvELO4716xaAZSIm9rLgZWjoivDdZjYpQAAg/ztnv/yRJIxxAQdwCa DVKb6+gVhDbxcGd/rk1XQ80Z8PTc0aV4idERfyDH8HdSIQDasmsBpqMsFjXdsxaTyyNY WM80QekaR01uQjRjfDUbfvuvReGdttrXPONBEz8LviAbMU1dCX0FYxIkRUJJnXB8xUiu aXWQ==
MIME-Version: 1.0
X-Received: by with SMTP id a14mr13385203wjx.84.1373319815337; Mon, 08 Jul 2013 14:43:35 -0700 (PDT)
Received: by with HTTP; Mon, 8 Jul 2013 14:43:35 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <> <> <> <>
Date: Mon, 8 Jul 2013 14:43:35 -0700
Message-ID: <>
From: Martin Thomson <>
To: Justin Uberti <>
Content-Type: text/plain; charset=UTF-8
Cc: "" <>
Subject: Re: [rtcweb] Fwd: New Version Notification for draft-uberti-rtcweb-turn-rest-00.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Jul 2013 21:43:38 -0000

On 8 July 2013 13:09, Justin Uberti <> wrote:
> The issue with using short term credentials, without a nonce, is the
> possibility of replay attacks by an eavesdropper.

It is no less vulnerable than having the long term credential set
(username, nonce, realm, and password) overheard.  Assuming that the
lifetime of the password is the same in both cases.  In either case,
the link that the eavesdropper is required to attack is the HTTP link.

> Passing realm and nonce solves this [...]

I was suggesting that since you have spent some very expensive
round-trips getting this information, there are no advantages in
spending yet another round-trip on a challenge.  I don't think that
passing realm and nonce is a good idea in practice - it creates a
tighter coupling between this new thing and the TURN server.

In practice, a master nonce is not quite what you need, you need a
nonce-generator function, or a line to the TURN server whereby you
query for every request you get.  The former imposes too-strong
constraints on implementations, the latter renders much of the
advantages of something like this moot.