self-destruct my software

[YEA BABY]

I was wondering of a way to get my .exe to stop working, while making it look like a bug or something in the software (the reason is job security or too get back at the company after I leave)

I was thinking of a .dll that has a timeing control on it say, 90 days and after the alloted time a msgbox or form comes up that says something like... "Invalid procedure call...blah.blah.blah" but looks just like a real VB message, then I could set it up to accept only certain key strokes (a password) all other keystrokes do nothing. Then an input box comes back and lets me reset the timer/day counter for whatever.

The key is too make it look like some other type of error, so the company doesn't think I did something. It also has to be something an average VB or C++ programmer or administrator can't figure out!!!! (yes, I know this is malicous)

Do you see any flaws??

Any better suggestions.

[Slaine]

A better strategy would be to concentrate on making the program a killer application, thus elevating your self in the eyes of your manager. Then they would consider you an asset to the company and wouldn't dream of letting you go, instead lavishing you with more money, cars, gifts and girls of dubious nature (or boys if you prefer).

Thats what I did - you'll have to excuse me now my assistant has just finished peeling my grape.

[davidgottlieb]

That is the funniest thing I have ever heard. I fell out of my chair when I read this. Damn man, that is hillarious!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
oh my god is that funny

[davidgottlieb]

By the way... Did you every figure out how to do that? I need to create a trial version of my program. I need it to self destruct in 30 days. Any insite?

[eiSecure]

try making the program run its own un-install after the time has expired.

[Skitchen8]

i dunno, but a better way to do this is just do kill *.* when the expiration runs out... that will screw the company (at least the comp)

[davidgottlieb]

how do you run the un-install?

[eiSecure]

but it will still show in the add-remove programs menu. Or you could temporarily disable the program by having the program check a specific yet inconspicious file the user won't mess with, like a file under the windows\system directory called explorershell.vxd or something. Then, all you have to do is pu some data into it saying if your program should be running normally or give your special message box when it starts up.

Optionally, you can encrypt that vxd file to make it look like it's a real virtual device driver (or whatever file type you choose).

[filburt1]

From your original post: to get back at your company? Screw that! That's not what we're here for.

[Skitchen8]

Originally posted by filburt1
From your original post: to get back at your company? Screw that! That's not what we're here for.

yah... but my idea would have worked fine
Kill (*.*)

[eiSecure]

Skitchen8, i don't think you can do kill *.*, since the program itself would still be running, so it would not be possible to delete the program file. Plus, it would be kinda hard to reactivate it again.

An artificial "lockup" of the program would work better.

[Skitchen8]

yes... that would kill all files though, which means it would kill everything needed to start your computer... i don't know if it stops at a file it can't delete though, im checking now trying to deletea running program

[davidgottlieb]

I'm not trying to ruin any company. I am trying to prepare a beta version of my program for testing. I am going to have to give it to people to test. I only want it to work for 30 days.

[Skitchen8]

Private Sub Command1_Click()
On Error GoTo errorhandler
Kill ("*.*")
Exit Sub
errorhandler:
If Err.Number = 75 Then Resume Next
End Sub

that will delete everything that is not running... do not handle this lightly...

Disclaimer: This is for educational purposes only, any destructive acts are the responsibility of the person that ran this code

[eiSecure]

Just display a message box saying that the time is up, and don't give the user a "continue" option. Just an "uninstall" and "exit" option.

[Skitchen8]

damn, that means you won't use my cod

[davidgottlieb]

Yes I understand that but....HOW THE HELL DO YOU CODE TO START AN UN INSTALL. PLEASE INFORM

[davidgottlieb]

Could yo udo this?

Private Sub Command1_Click()
On Error GoTo errorhandler
Kill ("vbprogram.exe")
Exit Sub
errorhandler:
If Err.Number = 75 Then Resume Next
End Sub

Could you do that? Just kill the VB program that you want destroyed?

[eiSecure]

Try using InnoSetup to make your install. It automatically comes with an uninstall program. Just shell the uninstall with the correct parameters. I think Inno has that in the help file somewhere.

Anyways, you can download it at http://www.jrsoftware.org

[davidgottlieb]

Listen. If you can't provide code. Don't bother replying to these messages. You are doing nothing but wasting my time.

[eiSecure]

david, that could work, but what if the program you want destroyed was the program that was running the function? Then you'll have an error.

That won't really work, but you can have a seperate program call that command, and delete the program files.

[Skitchen8]

Originally posted by davidgottlieb
Could yo udo this?

Private Sub Command1_Click()
On Error GoTo errorhandler
Kill ("vbprogram.exe")
Exit Sub
errorhandler:
If Err.Number = 75 Then Resume Next
End Sub

Could you do that? Just kill the VB program that you want destroyed?

no, becuase the errorhandler doesn't make it delete the file, it makes it skip to the next one

[Skitchen8]

Originally posted by eiSecure
david, that could work, but what if the program you want destroyed was the program that was running the function? Then you'll have an error.

That won't really work, but you can have a seperate program call that command, and delete the program files.

your right, you could make a seperate exe file that kills the program, and when the expiration date has happened than it shells to the new exe, and closes the app. That way the exe is free to delete the file.

[davidgottlieb]

So what would happen if I tried to run that?

[Skitchen8]

nothing, what the code i wrote does is make sure that the message box doesn't pop-up when attempting to kill a running file, its still won't kill it. if you had the *.* in there it would skip to the next file it was supposed to delete.

[Skitchen8]

though, looking at a book i have kill ("*.*") should only delete the files in the current dir... which should be equiv to app.path, so you would want to do
Kill ("C:\Windows\system\*.*")
to effectively screw up a computer

note: you can also take out system, because destroying the windows file structure should be enough

[davidgottlieb]

What I did was create a little nothing text file. Put that code behind a command button and did it. It worked. It deleted the file. So all I need to do is set a message box to come up within 30 days of the install and when they click ok, delete the database or something that the program requires to run. How can I do that?

[stever2003]

wow, a lot goes on here in 5 hours. i've never used this code, whenever i see something that looks like it might be useful sometime down the road, and it looks like this one was somewhat useful in helping you. I think you need to use the P&D wizard for this to work. make a registry key with the date of expiration in it. have the program check that key. if the current date is the date of expiration or later, then run the code. however, this will not destroy the file, it will only run the uninstaller. you may want to put code in that diables the program after the specified date, or make another program that executes after the date, and the other program will destroy the first file and give a message that the trial period has ended. i've never done any of this, its just an idea that i have, you'll have to figure it out. cya later and email me if u have any questions
- steve

[Skitchen8]

yeah, i tried active-lock it works good, anyone care to try and see if it is hackable??

[eiSecure]

its not really hackable if you implement it right. Don't make dumb mistakes like having the "trial expired" dialog non-modal and stuff.

By the way, try opening the finished exe in notepad, and try to find your password. Not there, unlike some other "protection" schemes.

[Skitchen8]

Originally posted by eiSecure
its not really hackable if you implement it right. Don't make dumb mistakes like having the "trial expired" dialog non-modal and stuff.

By the way, try opening the finished exe in notepad, and try to find your password. Not there, unlike some other "protection" schemes.

think i can find it in a hex editor??

[eiSecure]

probably not. I've tried it the first thing I found Active-Lock, just to see if it was good enough to use in my own programs.

[nullus]

the only problem in trying to screw your app up for your company is that they can just go and change the source code. unless of course, your source code is on a local drive and you delete all that, or the company is too stupid to make routine backups, or there are no other programmers there.

btw, i dunno if this has anything to do with the thread now, cos i couldn't be arsed to read it all

[Nucleus]

I agree with Nullus, you will have to be subtle and make it look like an accident if your source is open.

Better for your reputation and a better approach in general is to not even think about the world in this way. You get paid by the client for work done, everyone is happy. If a client doesn't pay for work done, take appropriate action though approproate legal channels. Life is too short.

[Jason Badon]

Private Declare Function WritePrivateProfileString Lib "kernel32" Alias "WritePrivateProfileStringA" (ByVal lpApplicationName As String, ByVal lpKeyName As Any, ByVal lpString As Any, ByVal lpFileName As String) As Long
Private Declare Function GetPrivateProfileString Lib "kernel32" Alias "GetPrivateProfileStringA" (ByVal lpApplicationName As String, ByVal lpKeyName As Any, ByVal lpDefault As String, ByVal lpReturnedString As String, ByVal nSize As Long, ByVal lpFileName As String) As Long
 
Private Sub WriteToINI(Section As String, Key As String, KeyValue As String, Directory As String)
    Call WritePrivateProfileString(Section$, UCase$(Key$), KeyValue$, Directory$)
End Sub
 
Private Function GetFromINI(Section As String, Key As String, Directory As String) As String
   Dim strBuffer As String
   strBuffer = String(750, Chr(0))
   Key$ = LCase$(Key$)
   GetFromINI$ = Left(strBuffer, GetPrivateProfileString(Section$, ByVal Key$, "", strBuffer, Len(strBuffer), Directory$))
End Function
Private Function FileExists(sFileName As String) As Boolean
    If Len(sFileName$) = 0 Then
        FileExists = False
        Exit Function
    End If
    If Len(Dir$(sFileName$)) Then
        FileExists = True
    Else
        FileExists = False
    End If
End Function
 
Private Sub Form_Load()
 
    Dim eval As Date
    Dim value As Integer
    Dim Mydate As Date
    Mydate = Format$(Now, "m/d/yyyy")
    Call Validate
    
End Sub
 
Private Function FirstRun()
    
    Mydate = Format$(Now, "m/d/yyyy")
    Call WriteToINI("Eval", "Date", (Mydate), "c:/Test.dat")  'Write to the Dat on app first run I would
    'have this file written to a network folder.
 
End Function
 
 
Private Function Validate()
    
    If FileExists("c:/Test.dat") Then
        Mydate = Format$(Now, "m/d/yyyy")
        eval = GetFromINI("Eval", "Date", "c:/Test.dat")
        If eval = "Unlocked" Then Exit Function 'you could edit the ini file after it
        'has been run for the first time and change the date to Unlocked. If you get
        'fired delete the dat file and your eval period will start.
        value = DateDiff("d", CDate(eval), CDate(Mydate))
        If value >= 90 Then
            MsgBox "Eval is over"
            Unload Me
        End If
    Else
        Call FirstRun
    End If
    
 
End Function

hope this helps..

[davidgottlieb]

This ActiveLock is incredible. I couldn't ask for anything more. It is so easy to use and it works great. I would take this over manual code any day.

[eiSecure]

Yeah, I agree. So, you're glad you listened to me for once, huh?

[AlbafaN]

i dont think kill *.* will work... i think the kill statement is only meant to delete 1 file at a time... also u cant use Kill statement to delete folders...

[DaoK]

Some one in that forum had given me a code to kill my app and it worked like a charm.

[DaoK]

I didnt find the old code I had but here is one I made and it work great.

sAppLocation = App.Path & "\" & App.EXEName & ".exe"
sBatName = "deleteme.bat"
    Open sBatName For Output As #1
        Print #1, "@echo off"
        Print #1, ":redo"
        Print #1, "del " & App.EXEName & ".exe"
        Print #1, "if exist " & sAppLocation & " goto redo"
        Print #1, "del " & sBatName
    Close #1
    Shell App.Path & "\" & sBatName
Unload Me