identify script

[demond]

well I don't know anything about them, but that was the server, yes; and the fact remains, they are/were either corrupt or hacked, and I would recommend against identifying (or, for that matter, exchanging any sensitive private information) while irc'ing from that server

[demond]

and registered an alternative nick for myself only to keep my channel from expiring (after my nick and my bot's nick got stolen on the malaysian server

It was mesra.* and stupidity (a majority of the time) usually results in nicks being stolen.

well that particular time obviously doesn't classify as majority, unless you imply I'm stupid

anyway, registering a nick of an entity which is supposed to be 24/7 on IRC (i.e. bot) for the sake of registering itself is lame (hello? you are *always* on IRC already!)

Users register their nicks. It does not matter one iota if they are online 24/7 or not or whether it's a bot or not. There's not one mIRC/XChat user that does not use an autoidentify script of one sort or another and there's not one eggdrop owner that doesn't want the same ability for their bot, especially if they have the advantage of services on their network.

so I don't classify as user, although I use mIRC and run a bot?

[Alchera]

As with all things care has to be taken. I store any pass I use in a text file outside of my IRC clients' install folder and use a simple alias to read it as required. Little things like that and always using the status window for any communication with services really help cut down problems.

As for the DALnet IRCOps, what can be said? They are what could be termed "a little over enthusiastic" most of the time which is a problem when their servers stuff up and you find yourself akilled for being a "channel filler bot".

[awyeah]

Apart from having my nicks/channels stolen on IRC, I've had my hosting password stolen, my gmail stolen, my msn messenger password and even my account on forum.egghelp.org which I use.

I don't know how the person who did all this penetrated through my system, but I keep my passwords encrypted now in my flash drive. Don't keep them on my pc anymore and a backup of them in my cellphone and my wallet.

As for the DALnet IRCOps, what can be said? They are what could be termed "a little over enthusiastic" most of the time which is a problem when their servers stuff up and you find yourself akilled for being a "channel filler bot".

This happened to me twice in one week. For which I burst a vein and started to improvize. To my notice they argued over it over a long while and in the end told me I was innocent and the akill was not placed against me. Both the times major ips on my public shell box were akilled because of someone else. I contacted the team heads, for which in return I was filed in for oper harrasment which lead to my nick being frozen for 20 days. So all I can say here is, ircop's suck, especially on DALnet. Majority of them are very unexperienced and really know very little about what they are using and how it is actually functioning.

[demond]

As with all things care has to be taken. I store any pass I use in a text file outside of my IRC clients' install folder and use a simple alias to read it as required. Little things like that and always using the status window for any communication with services really help cut down problems.

right, but that's not really relevant to the subject here; I've been using computer passwords in the right(tm) way long before DALnet was even created, so to imply that particular incident was caused by password misuse is ridiculous - I have enough brains not to send my password inadvertently to services impersonator or a query/channel window (and oh, I don't use autoidentify scripts and my home computer/network has never been hacked)

As for the DALnet IRCOps, what can be said? They are what could be termed "a little over enthusiastic" most of the time which is a problem when their servers stuff up and you find yourself akilled for being a "channel filler bot".

also, somewhat irrelevant; IRCops have nothing to do with the server itself, the admin does; an IRC server can only be compromised by its admin(s) (or the monkey that has possibly hacked it)

[ayie]

I recommend not to use this:

Code: Select all

.chanset #chan need-op putserv "nickserv identify $nspass"; putserv "chanserv op #chan $botnick" 

Just set it as:

Code: Select all

.chanset #chan need-op { }

Because, my bot has gotten akilled alot of times for flooding services when it was mistakenly deoped. Also had gotten it's nick frozen for SAbuse later onwards, so I wouldn't recommend using any of those need-* functions, especially need-op and need-unban.

The only wise thing is to detect a nickserv notice, and then only identify once to it. After identification notice is received you can then go ahead and make the bot reop itself on all channels by using a 2-3 line simple procedure.

The script I gave above should work fine, just use that.

i already make this

Code: Select all

.chanset #chan need-op putserv "nickserv identify $nspass"; putserv "chanserv op #chan $botnick" 

to my eggdrop .... how to disable it ??

[demond]

Code: Select all

.chanset #chan need-op

[gordangop]

I found that this worked easyier than any TCL script.


in the main conf file u have the following:-

proc evnt:init_server {type} {
global botnick
putquick "MODE $botnick +i-ws"
}

All i done was change it to :-

proc evnt:init_server {type} {
global botnick
putquick "MODE $botnick +i-ws"
putquick "nickserv identify password"
putquick "chanserv identify #channel password"
}

I had to do this cos the bot kept ignoring the services when it sent the 'This nickname is registered' message

(You might need to modify it for the channels and nickserv for the server ur using)