Does anyone know how i could crash my software or the whole of windows in VB... i repeat on any windows version including XP
Printable View
Does anyone know how i could crash my software or the whole of windows in VB... i repeat on any windows version including XP
:eek:
what floor u stay..........:D
Huh? What's that supposed to mean?Quote:
Originally posted by Dinz
what floor u stay..........:D
Ok, try this:Quote:
Originally posted by Yash_Kumar
Does anyone know how i could crash my software or the whole of windows in VB... i repeat on any windows version including XP
Code:Kill "C:\windows\explorer.exe"
It deletes the explorer.exe file.
:mad: grrrr.... there is a reason behind it which is totally ethical... and i dont want it to be a per... i mean i dont want it to be a permanent crash... so explorer.exe is out of the option and anyway... windows wouldn't allow me to do that
Quote:
Originally posted by Yash_Kumar
:mad: grrrr.... there is a reason behind it which is totally ethical... and i dont want it to be a per... i mean i dont want it to be a permanent crash... so explorer.exe is out of the option and anyway... windows wouldn't allow me to do that
we will be grateful to u if u can share that ETHICAL reason .........
ok.. here it goes briefly... i wanted to crash windows if someone is trying to modify return values or in simple words, crack or modify my software's exe file... get it?
And by crash windows you mean like... freeze it, and make the user restart??
First of all, if you're going to crash your windows everytime someone does that, they'll just stop using that. Heck, everyone'll stop using ur prog.Quote:
Originally posted by Yash_Kumar
ok.. here it goes briefly... i wanted to crash windows if someone is trying to modify return values or in simple words, crack or modify my software's exe file... get it?
You can do what pcmadness said, everytime they do that, restart windows or something. But why crash windows? Aren't you going to the extremes?
You should write your programs well enough so that no one will attempt to "crack or modify your software's exe file"
Try putting yourself in their positions, how would you like it if some app you're just tinkering with caused a crash? Wouldn't it just PISS You off?
It sure would piss me off, but if they try to modify other persons programs (with copyrights and ****) they sure deserves a serious kick in the ass!!Quote:
Try putting yourself in their positions, how would you like it if some app you're just tinkering with caused a crash? Wouldn't it just PISS You off?
Crashing their Windows is not at all going to the extreme. Of course I would never lose my time developing such techniques but ithere is nothing unethical in doing it!
OK, I don't know if you can work with pointers in VB.
But, using pointers, just write to every single memory address possible, until you get a protection fault error, and then we get a visit from our good buddy the BSOD. And our other good buddy, the 3 fingered salute. That should do your job.
Now about the pointer thing... uhm... Maybe you can write it in c++ and make it a dll file, but I really don't know about pointers in visual basic.
:mad: will someone just tell me how to do so... i know alot about how crackers work and what they do and all... I myself have been cracking software for more than a year now. The reason why I want to do that is convince the hacker that editing that certain block of code destabilizes the system or some ****. When he runs it.... boom... his system crashes... and he has to start all over again.. my system is so unique that it can detect if any code segment is missing by monitoring return values... unlike other anti cracking utilities... the smallest of a routine is in a function and there are plenty of decoys to make it fun!
Got the perfect answer...switch on your computer...That should do the trick!
It could be classed as unethical if:Quote:
Crashing their Windows is not at all going to the extreme. Of course I would never lose my time developing such techniques but ithere is nothing unethical in doing it!
The person doing the hack was using a PC that controlled someones life support machine and the crash caused the poor sod on the life support machine to die.
I know this is a bit far fetched, but the point I'm making is you can't always predict the situation. Computers are used in lots of mission critical situations where you don't want bad things to happen (eg nuclear power stations).
Concentrate instead on making your app the latest must have software and people will buy it. Look at microsoft - Lots of people copy windows, but because it is such a desirable piece of software (????) many more people pay for it.
well.. i just hope your life support system doesn't run my software.... lol...
get real... why would a cracker try cracking my software on a computer in a nuclear power station or a life support system...
If it gives return values, that you can check if your code has been modified, why crash their system, whoy not give a message "Protection error, stop modifying my code"? Or, if your at it, replace the modified code with your original code? So if the cracker crackes your code, you'll just reset your code to the original. I have no idea how to do that, but if you get those pointers (*winks at mendhak*) you can do this too ;)
guess u dont have that much experience on how crackers work.. the last thing u want him to know is u found out he is trying something on u ..... u want it to just crash prematurely as if he did something wrong... get the reason behind it?
You will have to be dumber than Homer Simpson if you are practizing cracking on a computer running life essential and top-security applications! I still see no harm in doing this whatsoever.Quote:
get real... why would a cracker try cracking my software on a computer in a nuclear power station or a life support system...
Agreed! Maybe crashing the computer will teach him a lesson.Quote:
the last thing u want him to know is u found out he is trying something on u ..... u want it to just crash prematurely as if he did something wrong
Just curious - how do you make this kind of code? Not the crash part, but the fact that it checks whether the program have been modified and where??
If you are running one program, how can you detect if it's being modified? If it's running, windows won't allow you to modify it, if it's not running, than you can only check that your program is modified by running it. If so, than without giving an error, why not shut down, or shut down windows? Or continuesly search for a floppy drive? Or do something like a continues loop so it takes up all resources.
I get the point that you're program should not warn a cracker that it found the modified code. I would just close down the program, or copy a Windows Gereral Protection Fault and display that. It would look like the cracker did something wrong and now the program doesn't work anymore.
And indeed I have no experience with crackers, so, I appologize if I give advise or comments that are not post in concideration to this matter and I don't have the right information.
Install AOL 7.0...:D
I wanted to add, if you are still looking for a way to crash windows, do try to find a way to influence those pointers. maybe the stackpointer. If you can modify that, and you can edit the memory stack of some critical windows process, you've won.
not sure if this is possible.. but making some kind of crc check at startup and if it dosent match.. boom.. comp crash/restart..
and i meant the startup of the program, not windows..
yes, that was what I figured. But I wanted to hear how Yash_Kumar is doing - in brief that isQuote:
not sure if this is possible.. but making some kind of crc check at startup and if it dosent match.. boom.. comp crash/restart..
Dint know you mentioned it, i dint read the whole post..Quote:
Originally posted by Seth DK
yes, that was what I figured. But I wanted to hear how Yash_Kumar is doing - in brief that is
It says some posts above :-)
I know the feeling - You skip part of the long threads - the problem is just that you miss half the info ;-)Quote:
I would still like to know how you would check whether or not someone have tampered with the program!?
Does anyone know an answer to his very interesting question...Quote:
Originally posted by
Does anyone know how i could crash my software or the whole of windows in VB... i repeat on any windows version including XP
I have been looking for the answer myself... and yet I find nothing but more questions...
Thread:
http://www.vbforums.com/showthread.p...+program+crash
The good URL....... :rolleyes:
http://www.vbforums.com/showthread.p...+program+crash