mirrors/coturn
1
0
Fork 0
mirror of https://github.com/coturn/coturn.git synced 2025-10-25 21:11:00 +02:00
Code Issues Projects Releases Wiki Activity

man page fix

Browse Source
This commit is contained in:
mom040267 2014-07-22 20:00:27 +00:00
parent 1b9c8e2a92
commit a8a2f91982
2 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README.turnserver
View File

@ -592,14 +592,15 @@ limited time by an application that has to create a TURN server connection.
The "classic" long-term credentials mechanism (LTCM) is described here: The "classic" long-term credentials mechanism (LTCM) is described here:
http://tools.ietf.org/html/rfc5389#section-10.2 http://tools.ietf.org/html/rfc5389#section-10.2
http://tools.ietf.org/html/rfc5389#section-15.4 http://tools.ietf.org/html/rfc5389#section-15.4
For authentication, each user must know two things: the username and the For authentication, each user must know two things: the username and the
password. Optionally, the user must supply the ORIGIN value, so that the password. Optionally, the user must supply the ORIGIN value, so that the
server can figure out the realm to be used for the user. The nonce and server can figure out the realm to be used for the user. The nonce and
the realm values are supplied by the TURN server. But LTCM is not saying the realm values are supplied by the TURN server. But LTCM is not saying
anything about the nature and about the persistence anything about the nature and about the persistence of the username and
of the username and of the password; and this is used by the REST API. of the password; and this is used by the REST API.
In the TURN REST API, there is no persistent passwords for users. A user has In the TURN REST API, there is no persistent passwords for users. A user has
just the username. The password is always temporary, and it is generated by just the username. The password is always temporary, and it is generated by

9
man/man1/turnserver.1
View File

@ -827,14 +827,15 @@ limited time by an application that has to create a TURN server connection.
The "classic" long\-term credentials mechanism (LTCM) is described here: The "classic" long\-term credentials mechanism (LTCM) is described here:
.PP .PP
http://tools.ietf.org/html/rfc5389#section\-10.2 http://tools.ietf.org/html/rfc5389#section\-10.2
.PP
http://tools.ietf.org/html/rfc5389#section\-15.4 http://tools.ietf.org/html/rfc5389#section\-15.4
.PP .PP
For authentication, each user must know two things: the username and the For authentication, each user must know two things: the username and the
password. Optionally, the user must supply the ORIGIN value, so that the password. Optionally, the user must supply the ORIGIN value, so that the
server can figure out the realm to be used for the user. The nonce and server can figure out the realm to be used for the user. The nonce and
the realm values are supplied by the TURN server. But LTCM is not saying the realm values are supplied by the TURN server. But LTCM is not saying
anything about the nature and about the persistence anything about the nature and about the persistence of the username and
of the username and of the password; and this is used by the REST API. of the password; and this is used by the REST API.
.PP .PP
In the TURN REST API, there is no persistent passwords for users. A user has In the TURN REST API, there is no persistent passwords for users. A user has
just the username. The password is always temporary, and it is generated by just the username. The password is always temporary, and it is generated by