mIRC Home    About    Download    Register    News    Help

Print Thread
#59572 09/11/03 12:58 AM
M
MageOfChrisz
MageOfChrisz
M
How would i go about disabling the /debug command in mIRC?
I know Alias Debug { halt } will disable it, but the person(s) would still be able to do /!debug.


#59573 09/11/03 01:42 AM
Joined: Feb 2003
Posts: 3,412
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Feb 2003
Posts: 3,412
Why do u want to halt that?? cos u must have a reason for it ?

#59574 09/11/03 02:03 AM
Joined: Dec 2002
Posts: 2,884
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Dec 2002
Posts: 2,884
You could probably create on INPUT events to block it, but then if a user realised that /debug wasn't working it wouldn't be hard to figure out that your script was blocking it. At which point they'd probably delete your script for trying to stop them accessing commands, which is highly suspicious in general.

#59575 09/11/03 02:03 AM
M
MageOfChrisz
MageOfChrisz
M
Quote:
Why do u want to halt that?? cos u must have a reason for it ?

I'm writing a account system for my bot that requires you have a password to login to it. It currently disables all pm windows (Thats how the login is recieved) so the bot owner cannot view the password.

/debug can allow them to view a password...

#59576 09/11/03 02:16 AM
Joined: Dec 2002
Posts: 2,884
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Dec 2002
Posts: 2,884
You mean you're trying to block the bot-runner from using /debug? Whoever's running the bot could simply change the code so he didn't need a password to login, or simply look at any data stored (unless it's been encrypted). Bottom-line, a person running a bot will always be able to view what's being sent to his computer, there's no way to stop that. Making your script try to dictate what someone can and cannot do within a program on their own computer like that comes off as very underhanded, I can say with certainty that any users of your script certainly won't appreciate it, and any users of the bot won't be 'protected' in any way because of it.

#59577 09/11/03 02:22 AM
M
MageOfChrisz
MageOfChrisz
M
Quote:
You mean you're trying to block the bot-runner from using /debug? Whoever's running the bot could simply change the code so he didn't need a password to login, or simply look at any data stored (unless it's been encrypted). Bottom-line, a person running a bot will always be able to view what's being sent to his computer, there's no way to stop that. Making your script try to dictate what someone can and cannot do within a program on their own computer like that comes off as very underhanded, I can say with certainty that any users of your script certainly won't appreciate it, and any users of the bot won't be 'protected' in any way because of it.

Spelling mistakes, grammatical errors, and stupid comments are intentional.


I would like malicious people that have no knowledge to stay away. Is that REALLY bad to ask for? The passwords are md5 encrypted when the bot recieves them. I don't think it's too much to ask if a bot has security over the password. Yes the script can be edited the way the user wants, if they want it that way, so be it, but i will not release it unsecure like that.

Last edited by MageOfChrisz; 09/11/03 02:24 AM.
#59578 10/11/03 07:51 AM
D
DaveC
DaveC
D
Dont try and disable the debug use it to recieve the passwords, and process them before they appear you can also stop the normal MSG windows ever existing for them as well by doing a momentary ignore of the nick, also the debuger alias can make a good method of regaining control. especially as it can sit in the alias'es and not the remotes, almost no one looks there for automated events.
Or
the debuger alias can set a flag that alows activation on each forthcoming event maybe using a time critical flag or flag value, if the flags are not set, then you know the /Debug has been reset by the owner of the bot, and you can shut down the script.


Link Copied to Clipboard