953609 - Send password to IRC servers known to use bots for authentification

Status: RESOLVED WORKSFORME

(Chat Core :: IRC, enhancement)

Description

[Instantbot]

*** Original post on bio 162 by Emil Tomassen <guice.slepasa AT gmail.com> at 2008-12-20 13:26:00 UTC ***

I don't seem to get the 'password'-thing to work for quakenet. I'm not sure if this field is supposed to be some kind of perform for authing, but as far as I can understand it doesn't work properly, since I have to msg Q-bot myself to auth although my pass is in the 'password'-field.

Thank you for an awesome IM-client!

Comment 1

[Florian Quèze [:florian]]

*** Original post on bio 162 at 2008-12-20 14:59:08 UTC ***

Currently, the password field of IRC accounts is only used to send a PASS command to the IRC server. For servers that use bots for the authentification, it doesn't work.

In pidgin the work around for this is the irchelper plugin (http://plugins.guifications.org/trac/wiki/irchelper).

I think we should look at similar approaches for Instantbird 0.2.
I'm tired of the noise caused currently by NickServers (on irc.mozilla.org and irc.freenode.net) with the current system.

Comment 2

[Florian Quèze [:florian]]

*** Original post on bio 162 at 2009-08-02 22:12:38 UTC ***

Removing the 0.2 target milestone that is just misleading here. I don't know when we will work on this, maybe for 0.3.

Comment 3

[Patrick Cloke [:clokep]]

*** Original post on bio 162 at 2010-11-08 03:27:09 UTC ***

Two ways I see this being done:
1. Have a checkbox "Authenticate to a nickserv" with a field for the nickserv (i.e. so you can set if its "nickserv" or "authserv" or some other bot name) name and for the password to auth with. (Note this would be separate from the "password" field so if both are used they can be?)
2. Have a generic method of running commands when various things happen (this is how a lot of IRC clients work, but is very use unfriendly for new users).

My plan was to implement 1 in the IRC rewrite (bug 953944 (bio 507)), thus assigning to me.

Comment 4

[Florian Quèze [:florian]]

*** Original post on bio 162 at 2010-11-08 07:04:44 UTC ***

(In reply to comment #3)

Have 2 separate places with different passwords for the same account seems strange to me.

Is there at least one known network where both the PASS command and an authentication to nickserv make sense and require a different password to be used?

If no, I would suggest we just use the account password to authenticate with the nickserv (however it is called on the network), and keep in the code of the IRC plugin (or a JSON string being the default value of a preference if you really want to have this configurable for advanced users) a map between the IRC connect server and the name of the authentication bot.

Comment 5

[Patrick Cloke [:clokep]]

*** Original post on bio 162 at 2010-11-08 13:22:09 UTC ***

(In reply to comment #4)
> (In reply to comment #3)
> Have 2 separate places with different passwords for the same account seems
> strange to me.
I agree, non-ideal and possibly confusing.
 
> Is there at least one known network where both the PASS command and an
> authentication to nickserv make sense and require a different password to be
> used?
I don't know of any that even use the PASS command.

> If no, I would suggest we just use the account password to authenticate with
> the nickserv (however it is called on the network), and keep in the code of the
> IRC plugin (or a JSON string being the default value of a preference if you
> really want to have this configurable for advanced users) a map between the IRC
> connect server and the name of the authentication bot.
Fair enough. I just think instead of hard coding "nickserv" we should have it configurable in some way. A preference works for me.

Comment 6

[Patrick Cloke [:clokep]]

*** Original post on bio 162 at 2010-12-20 04:22:59 UTC ***

The way I'm looking at doing this is adding a text field that has NickServ as the default value and can take other bots to authenticate to.

Comment 7

[Florian Quèze [:florian]]

*** Original post on bio 162 at 2010-12-20 09:46:31 UTC ***

(In reply to comment #6)
> The way I'm looking at doing this is adding a text field that has NickServ as
> the default value and can take other bots to authenticate to.

Are we sure the syntax of the authentication command doesn't change when the name is not NickServ?

Comment 8

[Patrick Cloke [:clokep]]

*** Original post on bio 162 at 2011-02-21 02:58:58 UTC ***

(In reply to comment #7)
> (In reply to comment #6)
> > The way I'm looking at doing this is adding a text field that has NickServ as
> > the default value and can take other bots to authenticate to.
> Are we sure the syntax of the authentication command doesn't change when the
> name is not NickServ?
No, we don't.

Also, it seems that irc.mozilla.org forwards the PASS command to NickServ, which seems like a better way to handle this then coding in nickserv names, but maybe an advanced option which is "Identify command" or something? And the user could do "/msg nickserv IDENTIFY <password>", where the "<password>" string is autofilled in by the program?

I also don't really like just blindly sending passwords to whatever the user put in there, using the PASS command the server (I assume) knows that NickServ is legitimate to send credentials to.

Comment 9

[Patrick Cloke [:clokep]]

*** Original post on bio 162 at 2011-03-03 15:51:27 UTC ***

Making this "NEW" as I'm not working on it right now. It's on my To-Do list though after I finish implementing protocol level stuff. Someone else can feel free to give me a patch though.

Comment 10

[Patrick Cloke [:clokep]]

*** Original post on bio 162 at 2012-02-27 15:37:52 UTC ***

Moving IRC bugs to new IRC component.

Comment 11

[Patrick Cloke [:clokep]]

*** Original post on bio 162 at 2012-07-16 16:53:04 UTC ***

See bug 954910 (bio 1477) for some of the issues with trying to identify whether NickServ is actually a bot or if it's just a random user posing as NickServ.

Comment 12

[Patrick Cloke [:clokep]]

*** Original post on bio 162 at 2012-11-21 20:02:15 UTC ***

I think this is fixed now that we send the IDENTIFY and NICKSERV IDENTIFY commands, does this now work on Quakenet?

Comment 13

[Patrick Cloke [:clokep]]

*** Original post on bio 162 at 2013-01-08 00:45:01 UTC ***

If there's a server that auto-identifying does not work on, please reopen this bug (or file a new one).