Projects tigase _server server-core Issues #293
TLS handshake config error (#293)
Closed
binh vo opened 1 decade ago

I had tried to config for the server with TLS handshake is required by adding the properties as below into the int.properties file.

--vhost-tls-required = true

But seems that it doesn't work since i sent the following stanza and receive the response successfully.

send :

<stream:stream xmlns:stream="http://etherx.jabber.org/streams" version="1.0" xmlns="jabber:client" to="binhvd" xml:lang="en" xmlns:xml="http://www.w3.org/XML/1998/namespace">

receive:

stream:features

PLAIN

ANONYMOUS

zlib

</stream:features>

send :

AHhnc2FkbWluADxwYXNzd29yZD48ZXRva2VuPmFzZGZnaGprbDwvZXRva2VuPjxzaXRlaWQ+MTIzNDU8L3NpdGVpZD48c2l0ZXVzZXJpZD4xMjM0NTY8L3NpdGV1c2VyaWQ+PHNpZ25hdHVyZT5kc2ZzZGZhZGZhZmFmPC9zaWduYXR1cmU+PC9wYXNzd29yZD4=

and finally receive :

Tigase version : 5.2.0 beta 3.

More a coup of questions:

How to config TLS version for the server to match with the client?

What happens if client use TLS v1.1 while the server using TLS v1.2? Will the user authentication timeout expired?

Artur Hefczyc commented 1 decade ago

I am not sure if 5.2.0 Beta3 does support TLS required option as I do not remember exactly when it was added. It might be not available in Beta3. Please try the 5.2.0 final. The final also has lots of fixes in TLS protocol and also hardened mode.

binh vo commented 1 decade ago

I have tested with 5.2.0 rc2 version and it works fine. Thank you.

issue 1 of 1
Type
Bug
Priority
Normal
Assignee
RedmineID
1772
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/server-core#293
Please wait...
Page is in error, reload to recover