Include long-term message integrity into indications

zhuguoqiang / rfc5766-turn-server

Automatically exported from code.google.com/p/rfc5766-turn-server

0 stars 0 forks source link

Include long-term message integrity into indications #54

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

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 indication it sends that would be harmless 
(the client may just ignore it) and it will provide better backward 
compatibility with older TURN servers (like turnserver.sourceforge.net).

Original issue reported on code.google.com by mom040...@gmail.com on 27 Aug 2013 at 3:41

GoogleCodeExporter commented 8 years ago

This is implemented in SVN and will be a part of 2.6.2.1 release.

Original comment by mom040...@gmail.com on 27 Aug 2013 at 3:41

Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 8 years ago

Original comment by mom040...@gmail.com on 27 Aug 2013 at 3:42

Added labels: Priority-Low
Removed labels: Priority-Medium

GoogleCodeExporter commented 8 years ago

Fixed in 2.6.2.1

Original comment by mom040...@gmail.com on 3 Sep 2013 at 7:13

Changed state: Fixed