mIRC Home    About    Download    Register    News    Help

Print Thread
Joined: Dec 2017
Posts: 4
H
Self-satisfied door
OP Offline
Self-satisfied door
H
Joined: Dec 2017
Posts: 4
depending on server, mirc reports
Quote
SSL wrong version number
Quote
SSL unexpected eof while reading

seems to be swallowing the cause and reporting the only ssl failure, which gives zero information, e.g.:

Quote
[24/01 01:06] Closing link: (***@***) [G-Lined: Excessive Services login failures. Your ban expires at about ***]
-
[24/01 01:06] * Disconnected
-
[24/01 01:06] * Connect retry #1 irc.***.net (+6697)
-
[24/01 01:06] * Unable to connect to server (SSL unexpected eof while reading)

Joined: Dec 2002
Posts: 5,443
Hoopy frood
Offline
Hoopy frood
Joined: Dec 2002
Posts: 5,443
The SSL messages listed in your post are standard SSL errors that are reported when a server closes a connection.

The most common reason for the "SSL wrong version number" error is that the server is using an old version of SSL that is not secure and a suitable protocol cannot be negotiated.

The "SSL unexpected eof while reading" is due to an old/non-compliant server that is not sending a close notify event ie. calling SSL_shutdown(), when closing the connection. OpenSSL 3.x introduced a vulnerability fix relating to truncation attacks where if the server does not send a close notify event, this error is reported to prevent the vulnerability.

As far as I see, there isn't much a client can do in this situation. The server itself needs to be updated.

Joined: Dec 2017
Posts: 4
H
Self-satisfied door
OP Offline
Self-satisfied door
H
Joined: Dec 2017
Posts: 4
i understand about the ssl errors, however the actual cause in this case is zline/gline.
is there no way to detect this? the ssl error is extremely misleading, as this is not a ssl problem at all (not only barking up the wrong tree, but doing it in the wrong forest...)
*lines are of course reported correctly when there is no ssl involved.

Joined: Dec 2002
Posts: 5,443
Hoopy frood
Offline
Hoopy frood
Joined: Dec 2002
Posts: 5,443
In your case, it looks like the SSL connection is reporting these errors before mIRC receives anything else. It is possible for a client to not receive pending outgoing messages from a server if the server closes the connection incorrectly. See here and here for discussions on this topic. The odds are that this is due to the way the server closes the connection. The fact that the behaviour is different with/without SSL is likely down to SSL itself being stricter in how it handles connections, eg. as in the case of the truncation vulnerability.


Link Copied to Clipboard