On Wed, Jun 26, 2013 at 11:16 AM, <[email protected]> wrote: > Usernames are uniquely assigned by the server to each client for each > media stream. ICE Passwords randomly generated for a group, and also > assigned by the server. > > I can change the flow so that the client signals the username that firefox > randomly generates back to the server, but this is not better than having > the server tell the client what user name and password to use. >
As I said in my previous comment, I am not sure that's true. The security analysis I pointed you at suggests otherwise. Whether the ice password is unique is not really my concern. Yes, but it is a security concern. > The app flow that I want is for the server to assign ice-ufrag and > ice-pwd to the client, and not the other way around. > > But at this point, since FF does not allow the application to assign the > ufrag/pwd, and it will be many months before FF would even potentially > allow it, I will have to change my application to accommodate firefox. > > Yes. Moreover, the standard is quite likely to prohibit this behavior. If you think it's an important behavior, you should engage on the RTCWEB list and explain why (a) it's important and (b) why you think the analysis in the draft is wrong. -Ekr _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
