Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Remove mention of lt-cred-mech in the sample coturn config. #4333

Merged
merged 2 commits into from
Dec 28, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog.d/4333.misc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Documentation improvements for coturn setup. Contributed by Krithin Sitaram.
5 changes: 2 additions & 3 deletions docs/turn-howto.rst
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,6 @@ You may be able to setup coturn via your package manager, or set it up manually
4. Create or edit the config file in ``/etc/turnserver.conf``. The relevant
lines, with example values, are::

lt-cred-mech
use-auth-secret
static-auth-secret=[your secret key here]
realm=turn.myserver.org
Expand All @@ -52,7 +51,7 @@ You may be able to setup coturn via your package manager, or set it up manually

5. Consider your security settings. TURN lets users request a relay
which will connect to arbitrary IP addresses and ports. At the least
we recommend:
we recommend::

# VoIP traffic is all UDP. There is no reason to let users connect to arbitrary TCP endpoints via the relay.
no-tcp-relay
Expand Down Expand Up @@ -106,7 +105,7 @@ Your home server configuration file needs the following extra keys:
to refresh credentials. The TURN REST API specification recommends
one day (86400000).

4. "turn_allow_guests": Whether to allow guest users to use the TURN
4. "turn_allow_guests": Whether to allow guest users to use the TURN
server. This is enabled by default, as otherwise VoIP will not
work reliably for guests. However, it does introduce a security risk
as it lets guests connect to arbitrary endpoints without having gone
Expand Down