You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use /connect IRCnet while not connected to a v6 capable net, I get a connection error trying to reach the v6 server, and then a TLS protocol error from the other server, even though that doesn't have a tls flag. If I interrupt with /rmreconns and give a new /connect IRCnet command, it works if the first server it tries is the non-TLS server, so it seems that the tls flag is stuck between connection attempts.
This is irssi 1.0.7 as found in Debian stable and 1.2.0 as found in Debian stable-backports.
The text was updated successfully, but these errors were encountered:
This was causing us to use the TLS settings from one server on another
which is not always appropriate. Instead, we now treat it like other
connection information and do not copy it. We get the TLS settings later
as appropriate when connecting.
Note there is still probably more that could be cleaned up here. For
example, the unix socket might be better treated as connection info too.
Fixesirssi#1027.
I have a TLS and a non-TLS server in the same rotation:
When I use
/connect IRCnet
while not connected to a v6 capable net, I get a connection error trying to reach the v6 server, and then a TLS protocol error from the other server, even though that doesn't have atls
flag. If I interrupt with/rmreconns
and give a new/connect IRCnet
command, it works if the first server it tries is the non-TLS server, so it seems that thetls
flag is stuck between connection attempts.This is irssi 1.0.7 as found in Debian stable and 1.2.0 as found in Debian stable-backports.
The text was updated successfully, but these errors were encountered: