Re: [rtcweb] End-to-end encryption vs end-to-end authentication (DTLS-SRTP / SDES-SRTP)

["Fabio Pietrosanti (naif)" <[e-mail]>]

On 4/5/12 7:42 PM, Roman Shpount wrote:
> 
> On Thu, Apr 5, 2012 at 1:07 PM, Fabio Pietrosanti (naif)
> <[e-mail] <mailto:[e-mail]>> wrote:
> 
>     This means that DTLS-SRTP, from a trust-model point of view, does not
>     provide end-to-end security because there will always be a trusted third
>     party able to authorize Man in the Middle to do eavesdropping.
> 
> 
> Incorrect. If fingerprint is exposed and can be verified, DTLS-SRTP does
> provide end-to-end security. No third parties involved.

No, you are wrong in the understanding.

The fingerprint is always delivered from the signaling services, so by
the HTTPS website providing the JS calling application.

>From :
                      RTCWEB Security Architecture
http://tools.ietf.org/html/draft-ietf-rtcweb-security-arch-01#section-4.1

4.1.  Initial Signaling
[...]

In either case, it will contain:

   o  Media channel information
   o  ICE candidates
   o  A fingerprint attribute binding the communication to Alice's
      public key [RFC5763]

[...]
   This message is sent to the signaling server, e.g., by XMLHttpRequest
   [XmlHttpRequest] or by WebSockets [RFC6455] The signaling server
   processes the message from Alice's browser


So basically the "signaling service" provide the fingerprint information.

Additionally, in case you want to trust the fingerprint verification via
an identity provider, please read below:
From:
		RTCWEB Generic Identity Provider Interface
http://tools.ietf.org/html/draft-rescorla-rtcweb-generic-idp-00#section-5.4.1

5.4.3.1.  Authenticating Party
[...]
   o  If a IdP is provided by the calling application use that.


The IdP is provide *by the signaling service*.


So basically:

- The user get the calling application from signaling service
- The user get the fingerprint from signaling service
- The user get the IdP from the signaling service


So basically the signaling service can ALWAYS do MITM and provide
eavesdropping services to authorized and non-authorized users.

>From a trust model point of view:

		DTLS-SRTP = SDES-RTP

Because in both case the "signaling service" is a trusted third party
able to intercept phone calls.

It's important to define clearly somewhere that "WebRTC does not provide
end-to-end security"

Fabio