-
```
Per RFC 5389, indications do not have to be authenticated and equipped with
message-integrity when the long-term mechanism is used. But if the server would
include message-integrity into the ind…
-
```
What steps will reproduce the problem?
1.install coturn
2.vi /etc/turnserver.conf
3.turnserver /etc/turnserver.conf
What is the expected output? What do you see instead?
I have installed the cotu…
-
```
What steps will reproduce the problem?
> grep \$ INSTALL
$ sudo dpkg -i turnserver-*-*.deb
What is the expected output? What do you see instead?
> grep \$ INSTALL
$ sudo apt-get install gdebi-cor…
-
```
Red Hat Enterprise Linux 6.4 / 64- bit i installed the server package.
Install:
$ cd /var/tmp;
wget
https://github.com/downloads/libevent/libevent/libevent-2.0.21-stable.tar.gz;
tar xvfz libev…
-
```
RFC 5389 says that Nonce values are valid server-wide:
If the client has not completed a successful request/response
transaction with the server (as identified by hostname, if the DNS
pr…
-
```
What steps will reproduce the problem?
> grep \$ INSTALL
$ sudo dpkg -i turnserver-*-*.deb
What is the expected output? What do you see instead?
> grep \$ INSTALL
$ sudo apt-get install gdebi-cor…
-
```
Per RFC 5389, indications do not have to be authenticated and equipped with
message-integrity when the long-term mechanism is used. But if the server would
include message-integrity into the ind…
-
```
According to RFC 5389, STUN Transaction IDs SHOULD be cryptographically random;
RFC 5766 similarly says that nonces SHOULD be cryptographically random, and
cites RFC 4086.
However, rfc5766-turn…
-
```
Per RFC 5389, indications do not have to be authenticated and equipped with
message-integrity when the long-term mechanism is used. But if the server would
include message-integrity into the ind…
-
```
What steps will reproduce the problem?
> grep \$ INSTALL
$ sudo dpkg -i turnserver-*-*.deb
What is the expected output? What do you see instead?
> grep \$ INSTALL
$ sudo apt-get install gdebi-cor…