Re: [MMUSIC] Handling of unverified data and media

How did ICE+TLS "come up" butween A and S without A knowing S's ICE
ufrag/pwd, and thus S's fingerprint?  I assume it does know S's fingerprint
before it can decrypt any media from/through S.

Now are you suggesting that the remote fingerprint be changed to G's
fingerprint?  In that case, a new DTLS handshake would take place, but only
after A know's G's fingerprint.

In both cases, A knows the fingerprint before being able to decrypt
incoming media.

The only way to be able to decrypt media before having the remote
fingerprint is if you can receive the ICE ufrag/pwd before the  DTLS
fingerprint.  And with WebRTC/JSEP, it's impossible to get the ICE
ufrag/pwd before the DTLS fingerprint.  Changing to a second/different
fingerprint after that doesn't change anything.

On Fri, Mar 31, 2017 at 8:52 AM Cullen Jennings <fluffy@iii.ca> wrote:

>
> Imagine a WebRTC browser called A sends an offer to a SBC called S.  S
> sends PR offer accepting data channel but not others. ICE comes up between
> A and S. A TLS channel comes up between A and S. S forwards the offer to
> gateway called G over SIP with no ICE. G sends a TLS connection to A that
> is relayed via G. So this new connection is in the same ICE context. The
> ICE goes between A and S. But the 2nd TLS goes between A and G but gateway
> by S.
>
> I realize a more complete description would be useful but hopefully that
> is enough to think about a bit.
>
>
>
> On Mar 30, 2017, at 2:14 PM, Peter Thatcher <pthatcher@google.com> wrote:
>
> We have a mailing list discussion (here), a bug (
> https://github.com/w3c/webrtc-pc/issues/849) and a PR (
> https://github.com/w3c/webrtc-pc/pull/1026#issuecomment-279238215) about
> this.  I've copied the following comments to the latter two, so I'm adding
> them here as well.
>
> TL;DR: I don't think unverified media is compatible with ICE+DTLS.  Here
> is why (you can go see the bug, too):
>
>
>    1.
>
>    You can *receive* DTLS from the remote side before receiving the
>    remote description (and thus fingerprint). This happens if the remote side
>    sends an ICE connectivity check and the local side sends a response and
>    then the remote side sends a DTLS packet.
>    2.
>
>    You cannot *send* DTLS from the local side before receiving the remote
>    description (and thus fingerprint). This is because you can't send an ICE
>    connectivity check until you have the remote ICE ufrag and pwd, and thus
>    can't get an ICE connectivity check response, and thus can't send DTLS.
>    This is because you can't send anything other than ICE until you get an ICE
>    connectivity check response.
>    3.
>
>    Since you can't send DTLS, you can't complete the handshake, and thus
>    can't extract the SRTP key.
>
>
> Maybe I'm missing something, but I think this is impossible.
>
> On Sat, Mar 25, 2017 at 1:12 PM Cullen Jennings <fluffy@iii.ca> wrote:
>
>
> On Mar 13, 2017, at 3:44 PM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
> My question is: is this something that’s causing problems in real
> deployments, and requires a change in the standard?
>
>
> 1-800 go fedex. See webrtc requirements documents from many years ago.
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>
>