|
wojciech.kapcia@tigase.net opened 5 years ago
|
|
|
I think I may have fixed it already… |
|
|
Done in commit:d6c84b345fe0d5f4efa227fbe0db4a1f5032fada |
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Version |
tigase-server-8.2.0
|
| Spent time |
4h 45m
|
| Subsystem |
s2s
|
Related
-
tigase-private/systems-maintenance/servers#319 You are not authorized to access this issue
-
tigase-private/systems-maintenance/servers#306 You are not authorized to access this issue
Issue Votes (0)
Watchers (0)
Currently Tigase operates s2s socket in uni-directional mode, which can cause issues, with the other server has some limitations (for example doesn't accept s2s but itself opens s2s connections as in case of #servers-306). We shouldn't allow communication on such CID until connection is not established and authorised in both directions (in case BiDi is not supported, see #issue #1131)
NOTE: This should only apply in case of incomming connection (we make sure that we can't send response); we shouldn't really care in reverse case as we would be interested only in sending packets.