egghelp.org community

[Exterus]

Hi.

I've been running a bot for a while now and I recently swtiched irc client to irssi from mIRC. After the switch, the bot won't accept my password when I try to log in via DCC. I know it's the correct password, but it still says "bad password".

Could it have something to do with the character/translation settings in irssi being different from what mIRC is using? If so, can I somehow make the bot accept my password?

I'm running version 1.6.18 on a debian box using en-US as a system language.

[Sir_Fz]

Try telneting into your bot's console and readd yourelf setting your password from your new client.
_________________
Follow me on GitHub

- Opposing

Public Tcl scripts

[strikelight]

Check your ident settings for your irssi... Make sure that it is the same ident reply as you previously had set for your mIRC client.

[Exterus]

Unfortunately, I don't have the possibility of accessing the console via telnet. But thanks for the suggestion nonetheless.

[Exterus]

[strikelight]

Perform a /whois on yourself from both mIRC, and from irsii.
It could be your host is added as for example, *!ident@host, from mIRC, and your irsii client may not be replying to ident, and your host may look like ~ident@host instead.

[Exterus]

[speechles]

The answer is probably simple, and one word. Encodings.
On your mirc client, did you enable utf-8 support? When setting the password are you using a language set other than english? Extended Symbols perhaps? Weird Characters?
You must apply these same settings to irsii if you answer yes. If you cannot apply these settings, you will need to type your password into an encoding convertor (find these online), and convert from the mirc encoding which was used (utf-8?) into the encoding irsii uses (unicode?). Then use that transcoded password to give the bot. Afterwards, change the password once your on the partyline:
.chpass <transcoded-old-pass-same-one-which-got-you-on-the-partyline> <new-pass-of-your-choosing>

also, see here for more info about the problems with irsii and encodings.

[Exterus]

Having used irssi extensively previously, I have already changed the encoding settins in irssi to UTF-8. Also, I am Swedish, so many people in the channels I frequent use the iso-8859-1 charset, so I have added recode support to be able to interpet that as well. This produces the same (apparently, at least) effect as what mirc does. The password is just lowercase letters and numbers.

I have now tried setting the terminal charset to both UTF-8 and iso-8859-1 (the only encodings/charsets I've ever used) to no avail. I've also removed the recode and tried recoding it in UTF-8 while using iso-8859-1. No luck.

Could a change in the bots host somehow have something to do with it? I notice now that the VPN tunnel host it previously used have now been replaced with its actual host.

[Exterus]

I just wanted to post and say that I finally solved the problem.

It was a rather stupid mistake on my part. I had completely forgotten that I had previously tried linking a bot from the the same linux box I'm now ircing from to the bot I am trying to get access too. So, the current bot associated my new host with the old bot (since I have the exact same host as the old bot did). I finally managed to get telnet access to the bot that's giving me all the trouble, so I removed the old bot from the botlist.

Everything is just peachy now.

Thanks for the time and help!