소스 검색

Imported Upstream version 4.1.0.1

Oleg Moskalenko 11 년 전
부모
커밋
b81c7e0968
4개의 변경된 파일56개의 추가작업 그리고 45개의 파일을 삭제
  1. 29 23
      README.turnserver
  2. 1 1
      man/man1/turnadmin.1
  3. 25 20
      man/man1/turnserver.1
  4. 1 1
      man/man1/turnutils.1

+ 29 - 23
README.turnserver

@@ -83,13 +83,14 @@ User database settings:
 
 -b, --userdb	User database file name (default - turnuserdb.conf),
 		for long-term credentials mechanism only.
-		This user file database is being dynamically checked while the turnserver 
-		is working, and the user accounts can be changed dynamically by
-		editing the database.
+		This user file database is being dynamically checked while the 
+		turnserver is working, and the user accounts can be changed 
+		dynamically by editing the database.
 				  
 -e, --psql-userdb	User database connection string for PostgreSQL.
-		This database can be used for long-term and short-term credentials mechanisms,
-		and it can store the secret value for secret-based timed authentication in TURN RESP API.
+		This database can be used for long-term and short-term 
+		credentials mechanisms, and it can store the secret value 
+		for secret-based timed authentication in TURN RESP API.
 		The connection string format is like that:
 		 
 		"host=<host> dbname=<dbname> user=<db-user> password=<db-user-password> connect_timeout=<seconds>" 
@@ -97,14 +98,16 @@ User database settings:
 		
 		Or:
 		
-		"postgresql://username:password@hostname:port/databasename" (for 9.x or newer Postgres). 
+		"postgresql://username:password@hostname:port/databasename" 
+		(for 9.x or newer Postgres). 
 		See the INSTALL file for more explanations and examples.
 		
 		Also, see http://www.PostgreSQL.org for full PostgreSQL documentation.
 				  
 -M, --mysql-userdb	User database connection string for MySQL or MariaDB. 
-		This database can be used for long-term and short-term credentials mechanisms,
-		and it can store the secret value for secret-based timed authentication in TURN RESP API.
+		This database can be used for long-term and short-term 
+		credentials mechanisms, and it can store the secret value for 
+		secret-based timed authentication in TURN RESP API.
 		The connection string format is like that:
 		 
 		"host=<host> dbname=<dbname> user=<db-user> password=<db-user-password> connect_timeout=<seconds>"
@@ -114,19 +117,21 @@ User database settings:
 		for full MySQL documentation.
 		
 -J, --mongo-userdb	User database connection string for MongoDB. 
-		This database can be used for long-term and short-term credentials mechanisms,
-		and it can store the secret value for secret-based timed authentication in TURN RESP API.
+		This database can be used for long-term and short-term 
+		credentials mechanisms, and it can store the secret value 
+		for secret-based timed authentication in TURN RESP API.
 		The connection string format is like that:
 		 
-		"mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
+		"mongodb://username:password@host:port/database?options"
 		See the INSTALL file for more explanations and examples.
 		
 		Also, see http://docs.mongodb.org/manual/
 		for full MongoDB documentation.
 		
 -N, --redis-userdb	User database connection string for Redis. 
-		This database can be used for long-term and short-term credentials mechanisms,
-		and it can store the secret value for secret-based timed authentication in TURN RESP API.
+		This database can be used for long-term and short-term
+		credentials mechanisms, and it can store the secret 
+		value for secret-based timed authentication in TURN RESP API.
 		The connection string format is like that:
 		 
 		"ip=<ip-addr> dbname=<db-number> password=<db-password> connect_timeout=<seconds>"
@@ -587,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:
 
 http://tools.ietf.org/html/rfc5389#section-10.2
+
 http://tools.ietf.org/html/rfc5389#section-15.4
 
-For authentication, each user must know two things: the username and the 
-password. Optionally, the user must supply the ORIGIN value, so that 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
 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 
-anything about the nature and about the persistence 
-of the username and of the password; and this is used by the REST API.
+anything about the nature and about the persistence of the username and 
+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 
 just the username. The password is always temporary, and it is generated by 
@@ -868,17 +874,17 @@ SEE ALSO
 
   WEB RESOURCES
 
-	project page:
+project page:
 
-	http://code.google.com/p/coturn/
+http://code.google.com/p/coturn/
 
-	Wiki page:
+Wiki page:
 
-	http://code.google.com/p/coturn/wiki/Readme
+http://code.google.com/p/coturn/wiki/Readme
 
-	forum:
+forum:
 
-	https://groups.google.com/forum/?fromgroups=#!forum/turn-server-project-rfc5766-turn-server/
+https://groups.google.com/forum/?fromgroups=#!forum/turn-server-project-rfc5766-turn-server
 
 ======================================
 

+ 1 - 1
man/man1/turnadmin.1

@@ -1,5 +1,5 @@
 .\" Text automatically generated by txt2man
-.TH TURN 1 "15 July 2014" "" ""
+.TH TURN 1 "22 July 2014" "" ""
 .SH GENERAL INFORMATION
 
 \fIturnadmin\fP is a TURN administration tool. This tool can be used to manage 

+ 25 - 20
man/man1/turnserver.1

@@ -1,5 +1,5 @@
 .\" Text automatically generated by txt2man
-.TH TURN 1 "15 July 2014" "" ""
+.TH TURN 1 "22 July 2014" "" ""
 .SH GENERAL INFORMATION
 
 The \fBTURN Server\fP project contains the source code of a TURN server and TURN client 
@@ -134,15 +134,16 @@ User database settings:
 \fB\-b\fP, \fB\-\-userdb\fP
 User database file name (default \- turnuserdb.conf),
 for long\-term credentials mechanism only.
-This user file database is being dynamically checked while the \fIturnserver\fP 
-is working, and the user accounts can be changed dynamically by
-editing the database.
+This user file database is being dynamically checked while the 
+\fIturnserver\fP is working, and the user accounts can be changed 
+dynamically by editing the database.
 .TP
 .B
 \fB\-e\fP, \fB\-\-psql\-userdb\fP
 User database connection string for PostgreSQL.
-This database can be used for long\-term and short\-term credentials mechanisms,
-and it can store the secret value for secret\-based timed authentication in TURN RESP API.
+This database can be used for long\-term and short\-term 
+credentials mechanisms, and it can store the secret value 
+for secret\-based timed authentication in TURN RESP API.
 The connection string format is like that:
 .RS
 .PP
@@ -151,7 +152,8 @@ The connection string format is like that:
 .PP
 Or:
 .PP
-"postgresql://username:password@hostname:port/databasename" (for 9.x or newer Postgres). 
+"postgresql://username:password@hostname:port/databasename" 
+(for 9.x or newer Postgres). 
 See the INSTALL file for more explanations and examples.
 .PP
 Also, see http://www.PostgreSQL.org for full PostgreSQL documentation.
@@ -160,8 +162,9 @@ Also, see http://www.PostgreSQL.org for full PostgreSQL documentation.
 .B
 \fB\-M\fP, \fB\-\-mysql\-userdb\fP
 User database connection string for MySQL or MariaDB. 
-This database can be used for long\-term and short\-term credentials mechanisms,
-and it can store the secret value for secret\-based timed authentication in TURN RESP API.
+This database can be used for long\-term and short\-term 
+credentials mechanisms, and it can store the secret value for 
+secret\-based timed authentication in TURN RESP API.
 The connection string format is like that:
 .RS
 .PP
@@ -175,12 +178,13 @@ for full MySQL documentation.
 .B
 \fB\-J\fP, \fB\-\-mongo\-userdb\fP
 User database connection string for MongoDB. 
-This database can be used for long\-term and short\-term credentials mechanisms,
-and it can store the secret value for secret\-based timed authentication in TURN RESP API.
+This database can be used for long\-term and short\-term 
+credentials mechanisms, and it can store the secret value 
+for secret\-based timed authentication in TURN RESP API.
 The connection string format is like that:
 .RS
 .PP
-"mongodb://[username:password@]host1[:port1][,host2[:port2],\.\.\.[,hostN[:portN]]][/[database][?\fIoptions\fP]]"
+"mongodb://username:password@host:port/database?\fIoptions\fP"
 See the INSTALL file for more explanations and examples.
 .PP
 Also, see http://docs.mongodb.org/manual/
@@ -190,8 +194,9 @@ for full MongoDB documentation.
 .B
 \fB\-N\fP, \fB\-\-redis\-userdb\fP
 User database connection string for Redis. 
-This database can be used for long\-term and short\-term credentials mechanisms,
-and it can store the secret value for secret\-based timed authentication in TURN RESP API.
+This database can be used for long\-term and short\-term
+credentials mechanisms, and it can store the secret 
+value for secret\-based timed authentication in TURN RESP API.
 The connection string format is like that:
 .RS
 .PP
@@ -822,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:
 .PP
 http://tools.ietf.org/html/rfc5389#section\-10.2
+.PP
 http://tools.ietf.org/html/rfc5389#section\-15.4
 .PP
-For authentication, each user must know two things: the username and the 
-password. Optionally, the user must supply the ORIGIN value, so that 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
 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 
-anything about the nature and about the persistence 
-of the username and of the password; and this is used by the REST API.
+anything about the nature and about the persistence of the username and 
+of the password; and this is used by the REST API.
 .PP
 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 
@@ -1125,8 +1131,7 @@ http://code.google.com/p/coturn/wiki/Readme
 .PP
 forum:
 .PP
-https://groups.google.com/forum/?fromgroups=#!forum/turn\-server\-project\-rfc5766\-turn\-server/
-.RE
+https://groups.google.com/forum/?fromgroups=#!forum/turn\-server\-project\-rfc5766\-turn\-server
 .PP
 ======================================
 .SS  AUTHORS

+ 1 - 1
man/man1/turnutils.1

@@ -1,5 +1,5 @@
 .\" Text automatically generated by txt2man
-.TH TURN 1 "15 July 2014" "" ""
+.TH TURN 1 "22 July 2014" "" ""
 .SH GENERAL INFORMATION
 
 A set of turnutils_* programs provides some utility functionality to be used