egghelp/eggheads community

The f-Flag was the problem

2003-02-21T01:46:51-04:00

Hallo all,

thank you for the answers.

I already have made a "# server[:port[:password]] "
in my config file.

But this wasn't the problem. The problem was the f-Flag. During
the flood from the server at reconnect, the NickServ is ignored as
well. So the bind couldn't trigger on NickServ-texts at all.

The tip with the strict host is also a good idea. It is really a security bottleneck to allow any user messages just the words to the bot
what nickserv does to make the bot identifying.

So now it works well.

Thank you all for your help. I hope the identify-scripts in the
download section would be changed with your opinions of
additional ideas, so no new Topic needed on Nickserv identifying.

Thanks @ all

LukasFledermaus

Statistics: Posted by Guest — Fri Feb 21, 2003 1:46 am

Nickserv Identify in IRC-Network

2003-02-20T13:04:43-04:00

it works for my eggdrop1.6.13 @euIRC

yeah, it works on connect on any netowork which forwards the pass to nickserv, but when the nick is used by an prior connection and the bot enters with his alternate nick, the linked nick will still stay and get autoop, but the bot wont be able to use any chanserv comments, quitting with the reply "permission denied". all the things helping are to send the auth to nickserv. also if the nickserv gets down, resets due netsplit or something like this, the nick gets unauthed and changed to guest*. but triggering to the notices from nickserv and chanserv the bots keeps always authed and ready to fight against lamers .

Statistics: Posted by De Kus — Thu Feb 20, 2003 1:04 pm

Nickserv Identify in IRC-Network

2003-02-20T12:30:08-04:00

# This is the bot's server list. The bot will start at the first server listed,
# and cycle through them whenever it gets disconnected. You need to change these
# servers to YOUR network's servers.
#
# The format is:
# server[:port[:password]]

it works for my eggdrop1.6.13 @euIRC

Statistics: Posted by arcane — Thu Feb 20, 2003 12:30 pm

hehe

2003-02-20T11:39:48-04:00

this is why i decited to give nickserv and chanserv global +f. this will exclued them from beeing ignored.
note: du can give them stict hosts like nickserv!services@euirc.net cause so you can be sure with a simple check handle == nickserv it is really nickserv messaging you and no fake service trying to foul your bot and get your auth password.

Statistics: Posted by De Kus — Thu Feb 20, 2003 11:39 am

Thank you for your comments

2003-02-20T01:55:22-04:00

Thank you all for your comments,

i see that there alternative ways to catch and something
wrong with my user flag.

But the server send a lot of messages during connect
and the bot may protect themself by ignoring this messages?

After a while when the connect to server is finished
my log always output following message:

"No longer ignoring *!*@irc.server.com (expired)"

What flag in conf or what flag wherever may occure this
kind of protection?

Thanks forward for your reply

Lukas

Statistics: Posted by Guest — Thu Feb 20, 2003 1:55 am

Nickserv Identify in IRC-Network

2003-02-17T05:23:43-04:00

According to that script, it will need both a user-record in the bot, and alseo to give that record the global +f flag.

Statistics: Posted by ppslim — Mon Feb 17, 2003 5:23 am

hmmm

2003-02-16T22:22:56-04:00

my script using bind

Code:

bind notc f|- "This nickname is registered and protected" handle:nickneed

while nickserv has a userrecord with exact host nick!ident@server.

Statistics: Posted by De Kus — Sun Feb 16, 2003 10:22 pm

Nickserv Identify in IRC-Network

2003-02-16T16:06:32-04:00

well, if you are lucky then NickServ isn't sending IDENTIFY string by 'user notice'. That NOTICE you can 'catch' with bind notc * *.
If it's not 'catched' by 'bind notc' function, your NickServ is useing server notice type.
You can 'catch' that with:

Code:

bind raw * NOTICE your_functionproc your_function {from keyword rest}{...}

try test it first with some putlog's to figure out output

PS. Send NickServ IDENTIFY request here with your 'bind notc * *', may be you matching something different

Statistics: Posted by Guest — Sun Feb 16, 2003 4:06 pm

Nickserv Identify in IRC-Network

2003-02-16T10:05:40-04:00

Hello all,

i currently tested all tcl-scripts which should automatically identify their
botnick at Nickserv.

They would not work.

I checked out, that "bind notc" would not be triggered if Nickserv says
'Please register your nick...'.

This is why they are not work.

Maybe some wrong settings in my config file or the NickServ itself would
not work like eggdrop needs.

For any little help i am appreciate

thanks forward

Lukas

Statistics: Posted by Guest — Sun Feb 16, 2003 10:05 am