Executable verification

Posts 1–8 of 8 · Page 1 of 1
Executable verification
Hi im asking how i could like make a launcher wich you HAVE to run to get the other program to run.
Like the launher checks for update(i know how to do that part)
Then it updates the exe(Wich means the .exe shouldnt be executed)
(You cant launch the program by double clicking, only launched trough launcher)

So i want like a verification that it only runs if launcher executes it.
(Cause that will keep the program up to date)
Quote Originally Posted by qddW$#%^jtyjtyj View Post
Hi im asking how i could like make a launcher wich you HAVE to run to get the other program to run.
Like the launher checks for update(i know how to do that part)
Then it updates the exe(Wich means the .exe shouldnt be executed)
(You cant launch the program by double clicking, only launched trough launcher)

So i want like a verification that it only runs if launcher executes it.
(Cause that will keep the program up to date)
A real easy solution is:

Your launcher processname is: techlaunch.exe

Then at your application:

Code:
    Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
        Dim teststr As String = ""
        For Each p As Process In Process.GetProcesses
            teststr = teststr & (p.ProcessName.ToLower)
        Next
        If teststr.Contains("techlaunch") Then
            MsgBox("")
        End If
    End Sub
Not perfect, can be faked.
But a simple example ^^
Just put some code in your main programs startup code to check for an update, if one is available start your updater running and close the .exe.
In the main executable, make it only run if its command line argument is "techial2" and then you can do: Process.Start("appnamehere", "techial2")
Quote Originally Posted by NOOB View Post
In the main executable, make it only run if its command line argument is "techial2" and then you can do: Process.Start("appnamehere", "techial2")
Easy to crack though, communication through the commandline is really easy to fake. One more secure method would be to use named pipes to communicate.
Make your launcher make a temporary file, And then make your program check if the file exists..If exists then start, if not it close..
And every time you open the launcher it creates the temporary file (To be able to start )
and when you close the launcher, the temporary file is deleted...Something like that..

Sorry my english..
Get the parent process, verify its checksum. If its aye okay, continue, else, DIEEEEE()!!!
Use the way that AlterIWnet uses. Rename the exe to an other format, like .dat, .wtf, or whatever else. And then makes the launcher to run that app. Add updater etc...
Process.Start("urapp.dat", Nothing, Nothing)
Posts 1–8 of 8 · Page 1 of 1

Post a Reply

Tags for this Thread

None

Talk with us