Jabber protocol needs update

[Der Jude]

Jabber servers are starting to migrate toward newer ciphers and are restricting usage of old ones.
This results in miranda not being able to login into plentiful of them.
None of these ciphers seem to be supported by miranda at the current given time:

Spoiler

Code: [Select]

ECDHE-RSA-AES256-SHA384 (0xc028)
ECDHE-RSA-AES256-SHA (0xc014)
DHE-RSA-AES256-SHA256 (0x6b)
DHE-RSA-AES256-SHA (0x39)
AES256-SHA256 (0x3d)
AES256-SHA (0x35)
ECDHE-RSA-AES128-SHA256 (0xc027)
ECDHE-RSA-AES128-SHA (0xc013)
DHE-RSA-AES128-SHA256 (0x67)
DHE-RSA-AES128-SHA (0x33)
AES128-SHA256 (0x3c)
AES128-SHA (0x2f)

[close]

https://www.openssl.org/docs/apps/ciphers.html#tls_v1_2_cipher_suites
Please take care of it!

[ghazan]

TLS 1.2 is completely supported by Windows 7 SP1 and later.
thus we don't have to bother about it at all, cause we use the Windows embedded security.

Windows XP SP3 clients might be at risk, because MS stopped to support it, but we'd never use openssl

[Der Jude]

Oh so that's an issue with xp.
My calculatorpc is too weak for 7/8.
How about using openssl only for tls1.1/1.2 when its detected that miranda is running on legacy OS without new tls support?

[ghazan]

someone promised to provide a working patch for the kernel, but... you know how it usually goes
the distance between a wish & an action is really of the cosmic scale

[AnrDaemon]

My calculatorpc is too weak for 7/8.

You'd be surprised, how much LESS load Win7 cause to the system, compared to XP.

[White-Tiger]

You'd be surprised, how much LESS load Win7 cause to the system, compared to XP.

or 8 Though both use more system memory... but that's also part of the reason why they are faster (at least at drawing windows)
One reason why they won't run on really old PC's is that they use more CPU features such as SSE which in turn speeds up things. Any 64bit CPU should be fine though.

[AnrDaemon]

Actually, Win8 use even less memory. Don't trust the numbers blindly.