Votebot should use NickServ accounts instead of hostnames for admins.

Bug #483163 reported by Montel Edwards
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VoteBot
Confirmed
Wishlist
Unassigned

Bug Description

I believe Votebot should use NickServ accounts instead of the hostnames because some people can't get cloaks, either because the network they are using the bot does not give cloaks, they are using a webchat like the Freenode webchat, or other reasons.

It would be best though if the user could choose hostname or NickServ authentication when running the initial setup.pl file.

Montel Edwards (montel)
description: updated
Revision history for this message
Robb Munson (r.munson) wrote :

be advised that you do not HAVE to use a "cloak" from freenode, its advised but not absolutely necessary. You may still add your ip address that is not unaffiliated, its a little more of a security hazard but its still available.

Revision history for this message
Robb Munson (r.munson) wrote :

that said you can add ip98-181.2.4-whatever.cox.whatever if you wish, the bot reads the config file for what it is, it doesnt judge you if youre not using the cloaks.

Changed in votebot:
status: New → Won't Fix
Revision history for this message
Robb Munson (r.munson) wrote :

setting as wont fix for now due to comments above.

Changed in votebot:
importance: Undecided → Wishlist
Revision history for this message
Montel Edwards (montel) wrote : Re: [Bug 483163] Re: Votebot should use NickServ accounts instead of hostnames for admins.

I realize that you do not need to have a cloak, but it would help if it
could use NickServ. Nathan was the one that told me to file this bug.

On Sun, 2009-11-15 at 21:54 +0000, Robb Munson wrote:
> that said you can add ip98-181.2.4-whatever.cox.whatever if you wish,
> the bot reads the config file for what it is, it doesnt judge you if
> youre not using the cloaks.
>
> ** Changed in: votebot
> Status: New => Won't Fix
>

Revision history for this message
Robb Munson (r.munson) wrote :

well, ok then....this is the first time I have ever heard of this....sounds like the developers need to have a pow-wow :) (off topic banter, but yes)

Changed in votebot:
status: Won't Fix → Confirmed
Revision history for this message
Robb Munson (r.munson) wrote :

changed to confirmed.

Revision history for this message
Montel Edwards (montel) wrote :

This really doesn't bother me now that I have a PDPC cloak :)

Revision history for this message
Robb Munson (r.munson) wrote :

Sadly, now I like this as it would cut down the size of the config files.

Revision history for this message
Montel Edwards (montel) wrote : Re: [Bug 483163] Re: Votebot should use NickServ accounts instead of hostnames for admins.

Well, all the bot would have to do is /whois and look for which
account it's identified onto.

But, I think that it should be an option that is asked in the setup.pl
to make it compatible for networks that do not offer NickServ

On Mon, Jan 18, 2010 at 9:58 PM, Robb Munson <email address hidden> wrote:
> Sadly, now I like this as it would cut down the size of the config
> files.
>
> --
> Votebot should use NickServ accounts instead of hostnames for admins.
> https://bugs.launchpad.net/bugs/483163
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Robb Munson (r.munson) wrote :

A little compromise, how bout this show the names of the admins in the config file, have the bot look for "%admin is identified to services" in the bot itself, take out the whole hostmask lookup thing...

Revision history for this message
Robb Munson (r.munson) wrote :

then again even that...meh..

Revision history for this message
Robb Munson (r.munson) wrote :

Have the bot have an admin password, only give it out to our admins, make the bot search for the host of the admin when they issue the .password command, if they dont match the host then no dice, they arent getting in.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.