mIRC Home    About    Download    Register    News    Help

Print Thread
/server with pass #260026 20/02/17 03:59 PM
Joined: Apr 2010
Posts: 959
F
FroggieDaFrog Offline OP
Hoopy frood
OP Offline
Hoopy frood
F
Joined: Apr 2010
Posts: 959
In previous versions the following could be used to send a server password:
Code:
/server <server>:<port> <pass>
/server <server> <port> <pass>


Now the following is required in the latest beta, where "-l pass" is literal text:
Code:
/server <server:port> <pass> -l pass


This breaks backwards compatibility, and seems obtuse compared to how most builtin commands work, so I assume the change is unintented

Last edited by FroggieDaFrog; 20/02/17 04:14 PM.

I am SReject
My Stuff
Re: /server with pass [Re: FroggieDaFrog] #260029 20/02/17 04:49 PM
Joined: Feb 2003
Posts: 2,742
Raccoon Offline
Hoopy frood
Offline
Hoopy frood
Joined: Feb 2003
Posts: 2,742
Similar topic here; different(?) bug I'd like to report for beta v7.47.489

All of my ZNC servers I have saved will not connect. They all have passwords (as required by ZNC). The method is "Server Password (/PASS)" (default).

Watching the /debug window, the PASS command is not being sent.

-> 123.123.123.123 CAP LS
-> 123.123.123.123 NICK Raccoon
-> 123.123.123.123 USER racccoon 0 * :raccoon
<- :irc.znc.in CAP unknown-nick LS :userhost-in-names multi-prefix znc.in/server-time-iso znc.in/batch znc.in/self-message
-> 123.123.123.123 CAP REQ :userhost-in-names
-> 123.123.123.123 CAP REQ :multi-prefix
-> 123.123.123.123 CAP REQ :znc.in/server-time-iso
<- :irc.znc.in CAP Raccoon ACK :userhost-in-names
<- :irc.znc.in CAP Raccoon ACK :multi-prefix
<- :irc.znc.in CAP Raccoon ACK :znc.in/server-time-iso
-> 123.123.123.123 CAP LIST
-> 123.123.123.123 CAP END
<- :irc.znc.in CAP Raccoon LIST :multi-prefix userhost-in-names znc.in/server-time-iso
<- :irc.znc.in 464 Raccoon :Password required
<- :irc.znc.in NOTICE AUTH :*** You need to send your password. Configure your client to send a server password.
<- :irc.znc.in NOTICE AUTH :*** To connect now, you can use /quote PASS <username>:<password>, or /quote PASS <username>/<network>:<password> to connect to a specific network.


Suggestion: At numeric 464 "Password required" you might send along the PASS command command as a failsafe measure, too, regardless of the selected non-encrypted authentication method chosen by the user.

On a design note: I recommend always sending the PASS command, even if a user chooses SASL PLAIN, as it typically behaves as a fallback method of authentication. That is, if SASL PLAIN fails to authenticate in time due to laggy services or netsplits, the PASS command will lag along in queue and may eventually find its destination. But that's surely up for argument, too. But PASS + SASL PLAIN together has never hurt anybody.

Last edited by Raccoon; 20/02/17 05:09 PM.

Well. At least I won lunch.
Good philosophy, see good in bad, I like!
Re: /server with pass [Re: FroggieDaFrog] #260030 20/02/17 05:14 PM
Joined: Dec 2002
Posts: 4,894
Khaled Offline
Hoopy frood
Offline
Hoopy frood
Joined: Dec 2002
Posts: 4,894
Thanks this issue has been fixed for the next beta.

Re: /server with pass [Re: Khaled] #260031 20/02/17 05:24 PM
Joined: Feb 2003
Posts: 2,742
Raccoon Offline
Hoopy frood
Offline
Hoopy frood
Joined: Feb 2003
Posts: 2,742
Oh, I think I narrowed down the bug for the server list. If I Edit the server > Change from the default "Server Password (/PASS)" to an alternate (eg: SASL) method > hit OK > Edit the server again > Change back to "Server Password (/PASS)" > hit OK > click Select > Connect -- My ZNCs will connect, now.

mIRC doesn't honor the default /PASS method for old servers.ini files where no method exists for that server entry.


Well. At least I won lunch.
Good philosophy, see good in bad, I like!