From: Juliusz Chroboczek <jch@irif.fr>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Cell <galene.org@kn1ght.org>, galene@lists.galene.org
Subject: [Galene] Re: coturn config
Date: Tue, 29 Dec 2020 02:56:38 +0100 [thread overview]
Message-ID: <87k0t1e5nt.wl-jch@irif.fr> (raw)
In-Reply-To: <8735zpya4m.fsf@toke.dk>
> ...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?
-- Juliusz
next prev parent reply other threads:[~2020-12-29 1:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 16:57 [Galene] " Cell
2020-12-27 17:55 ` [Galene] " Toke Høiland-Jørgensen
2020-12-27 18:02 ` Cell
2020-12-27 18:06 ` Cell
2020-12-27 18:16 ` Toke Høiland-Jørgensen
2020-12-27 19:04 ` Juliusz Chroboczek
2020-12-27 19:27 ` Juliusz Chroboczek
2020-12-27 20:32 ` Toke Høiland-Jørgensen
2020-12-27 23:28 ` Juliusz Chroboczek
2020-12-28 1:38 ` Toke Høiland-Jørgensen
2020-12-28 18:49 ` Juliusz Chroboczek
2020-12-28 19:59 ` Toke Høiland-Jørgensen
2020-12-29 1:56 ` Juliusz Chroboczek [this message]
2020-12-29 2:09 ` Toke Høiland-Jørgensen
2020-12-29 8:35 ` Michael Ströder
2021-01-01 22:55 ` Juliusz Chroboczek
2021-01-01 23:43 ` Gabriel Kerneis
2021-01-02 0:02 ` Juliusz Chroboczek
2021-01-07 12:07 ` Michael Ströder
2021-01-07 12:14 ` Toke Høiland-Jørgensen
2021-01-07 12:31 ` [Galene] logging (was: coturn config) Michael Ströder
2021-01-07 13:27 ` [Galene] Re: coturn config Juliusz Chroboczek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0t1e5nt.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene.org@kn1ght.org \
--cc=galene@lists.galene.org \
--cc=toke@toke.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox