Problem with scripted server connection and SASL - 14/06/17 03:16 PM
Hello,
First of all, thanks for still maintaining the program I have used for the longest time (I have used mIRC continuously since I got dialup in the late 90s).
I just updated to 7.49, and I can't seem to reliably log in to the Freenode or EsperNet networks anymore.
I have used for a long time a small script to automatically use /server -m to connect me to my usual servers.
In 7.48, I was able to configure a server to use CAP SASL, and the "/server -m irc.esper.net" would properly use the right authentication method, and send the proper user/password for the login.
However, in 7.49, this is no longer true. When I run the command, the protocol dump looks like:
It seems that mirc 7.49 has troubles applying the right login settings when using the /server command without any password parameter, and I really hope that this is not by design, because it breaks one of my my most essential scripts (I really do not want to embed the plaintext password in a script file).
First of all, thanks for still maintaining the program I have used for the longest time (I have used mIRC continuously since I got dialup in the late 90s).
I just updated to 7.49, and I can't seem to reliably log in to the Freenode or EsperNet networks anymore.
I have used for a long time a small script to automatically use /server -m to connect me to my usual servers.
In 7.48, I was able to configure a server to use CAP SASL, and the "/server -m irc.esper.net" would properly use the right authentication method, and send the proper user/password for the login.
However, in 7.49, this is no longer true. When I run the command, the protocol dump looks like:
Code:
-> irc.esper.net CAP LS 302 -> irc.esper.net PASS LM2?LM1?gigaherz:PASSWORD_HERE_CENSORED -> irc.esper.net NICK gigaherz -> irc.esper.net USER giga 0 * :the one <- :ranger.esper.net NOTICE * :*** Looking up your hostname... <- :ranger.esper.net NOTICE * :*** Checking Ident <- :ranger.esper.net NOTICE * :*** Found your hostname <- :ranger.esper.net NOTICE * :*** Got Ident response <- :ranger.esper.net CAP * LS :account-notify away-notify cap-notify chghost extended-join multi-prefix sasl tls userhost-in-names -> irc.esper.net CAP REQ :account-notify -> irc.esper.net CAP REQ :away-notify -> irc.esper.net CAP REQ :chghost -> irc.esper.net CAP REQ :extended-join -> irc.esper.net CAP REQ :multi-prefix -> irc.esper.net CAP REQ :userhost-in-names <- PING :238DF2F0 -> irc.esper.net PONG :238DF2F0 <- :ranger.esper.net CAP gigaherz ACK :account-notify <- :ranger.esper.net CAP gigaherz ACK :away-notify <- :ranger.esper.net CAP gigaherz ACK :chghost <- :ranger.esper.net CAP gigaherz ACK :extended-join <- :ranger.esper.net CAP gigaherz ACK :multi-prefix <- :ranger.esper.net CAP gigaherz ACK :userhost-in-names -> irc.esper.net CAP LIST -> irc.esper.net CAP END <- :ranger.esper.net CAP gigaherz LIST :account-notify away-notify chghost extended-join multi-prefix userhost-in-names <- :ranger.esper.net 001 gigaherz :Welcome to the EsperNet Internet Relay Chat Network gigaherz -> ranger.esper.net USERHOST gigaherz <- :ranger.esper.net 002 gigaherz :Your host is ranger.esper.net[168.235.75.5/6697], running version charybdis-3.5.3 ... continues ...
It seems that mirc 7.49 has troubles applying the right login settings when using the /server command without any password parameter, and I really hope that this is not by design, because it breaks one of my my most essential scripts (I really do not want to embed the plaintext password in a script file).