From mboxrd@z Thu Jan 1 00:00:00 1970 From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1609207747; bh=m6bEb4scL2DOdvC7SaTyRaCTV2GbApUb0b8rNFn4OS8=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Q/RWMBQf6FpSa6Wz1XvYTjKQ/ULKD7eyc0Ak9ltQl5Ciz6dfaDNZ8J2nvtpjO856s xwx7m4M9tXq5h0NE9TSLaj+iAvJuJEtJe9dbHM189YEcdyL4hZ1W04Br/G47gCj9ur 8M9C9Gv0RgbMrzTZkfD2m2yK7mcAuVfc1gCPIa9SJZ362ZlKYgcz5d5WMWGog/3Cbk O5dyvVlfl5WbNPz6/YIAPpHLxANXZxb92trG4QRQJTYOwESr29w85O+QY7vAWDxwOx YuLxsFdxoszyaXpEg4aa4S/03cmZ3jqfWFfQArHtwjSt+0JsWLHm9VJk3FOIlkhPOi lMD7xddcG0pzg== To: Juliusz Chroboczek In-Reply-To: <87k0t1e5nt.wl-jch@irif.fr> References: <1082cfcde178ddb72b51bcd03ee6770a@kn1ght.org> <87zh1zt6ip.wl-jch@irif.fr> <87y2hjt5fx.wl-jch@irif.fr> <87y2hjxa64.fsf@toke.dk> <87r1nau8v0.wl-jch@irif.fr> <87sg7qyaj2.fsf@toke.dk> <87a6tx7olm.wl-jch@irif.fr> <8735zpya4m.fsf@toke.dk> <87k0t1e5nt.wl-jch@irif.fr> Date: Tue, 29 Dec 2020 03:09:07 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87v9clnz24.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Message-ID-Hash: MY4TAJDVZXBMHCP53YBZPTRXHI4FPEEV X-Message-ID-Hash: MY4TAJDVZXBMHCP53YBZPTRXHI4FPEEV X-MailFrom: toke@toke.dk X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: Cell , galene@lists.galene.org X-Mailman-Version: 3.3.2 Precedence: list Subject: [Galene] Re: coturn config List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: Juliusz Chroboczek writes: >> ...And it turns out that I completely misunderstood how this is supposed >> to work: > > Yeah, so did I. What coturn apparently implements makes a lot more sense > than what the draft describes. > > Apparently, the credentials are computed deterministically from the > username and a shared secret. In order to avoid replay, a timestamp is > encoded within the username (phooey). Since both servers perform the same > computation, there is no need for the brittle HTTP-based protocol. See > > https://github.com/coturn/coturn/blob/master/examples/etc/turnserver.conf#L209 > > Supposing I decide to implement this -- any ideas how this should be > configured? Well, Nextcloud Talk just takes server name/port, shared secret, and whether to use UDP, TCP or both. The interval is hard-coded, and the userid random as in the code I pasted before. So replicating that would be fine with me. I seem to recall BBB had a similar config option... -Toke