@ KingTomato:
I never answered on spelling flames on UseNet, and I don't do it here.
@LocutusofBorg
Hmmm I think you didn't quite catch what I meant.
I was talking about SHS/VBS/whatever files that simply overwrite the mirc.ini file. Not more, not less. MANY of them spreading over IRC via socket operations, i.e. the ROL.VBS worm
And: My idea was to disable ON SOCKET, SOCKLISTEN etc. commands by default, but if the user needs them, to enable them in the options.
About the drive serial: Well, mirc stores settings in the mirc.ini file. So I just wanted to create a protection what makes it not possible to re-enable that locked functions by simply replacing the .ini file. Not less, not more. I just wanted to put some obstacles in the way that makes it difficult for viruses/worms/however-KingTomato-would-call-them to spread/activate some TYPICAL functions.
The thing is: Users who know what they're doing, they will activate functions manually (and I guess, they won't open I'm-soooo-sexy.jpg.bat.pif.vbs.html.shs.com.exe files). Users who don't, they can just use mIRC for what it's made for: chatting. Now, often they just wonder why they get banned/killed/k-lined etc. and cannot use the server at all - and cannot ask ANY help channels because they can't connect.
@Raccoon
Surely, there is no ABSOLUTELY protection. But imagine this:
Maybe you have a high security door with camera, fingerprint detection, eye scanner, 16-digit PIN code, voice acknowledge and five locks with high security level what never can be picked by unauthorized persons. And you have an open garage at the back side of the house that is open by default and has a simple door to your kitchen. If you've got an intruder, where would he enter the house? My idea was just to close the garage door; if somebody need it to open, he would do it.
