-
I fixed the NPE by including additional check. However, that wouldn't allow connections from the server. Original issue (#issue #1309) was caused only for incoming connections having random
to
addresses. So to avoid generating odd certificates (by only allowing connections with properto
) and considering RFC: "Interoperability Note: It is possible that implementations based on [RFC3920] will not include the 'from' address on any stream headers (even ones whose confidentiality and integrity are protected); an entity SHOULD be liberal in accepting such stream headers." I opted to verifying that onlyto
header is present and correct.I think it should be fine at this point, what od you think @andrzej.wojcik ?
-
On a semi-related note,
jabbercity.ru
got updated to more recent ejabberd:<iq id='ver' type='get' to='jabbercity.ru'> <query xmlns='jabber:iq:version'/> </iq> <!-- 2022-12-26T21:22:51Z <<<< --> <iq from='jabbercity.ru' xmlns='jabber:client' to='wojtek@tigase.org/966238979-tigase-2' id='ver' type='result'> <query xmlns='jabber:iq:version'> <name>ejabberd</name> <version>22.10.0</version> </query> </iq>
-
I think that verifying only
to
header is good as it would allow other servers to connect to us as long as they support RFC. In my opinion that is very good and other servers (such asjabbercity.ru
) should be updated (they had over 5 years old version of ejabberd).
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Version |
tigase-server-8.4.0
|
-
tigase-server-8.4.0 Closed