Remote Server Control

[Syst3m_W1z4rd]

The example I will give is just for Hybrids. I would suggest make an extern application in your server project, it's not efficient to do it in the game- or authserver.

Download:


In Program.cs set IP and Port.

Commands now:

/disconnect
/restart
/close processname

The way it work is, you enter a password.
It sends the command through bytes and then it checks if password is correct serverside. It's having "ServerCMD", so the server knows it's a remote command, but you can remove that if you make an extern application for your cmdserver.

Example for Hybrids source.

 Spoiler

Find: (In Game Processor.cs)

static unsafe void Game_ReceivePacket(NetworkClient nClient, byte[] Packet)

Right under the first { put this:

            if (RemoteControl.Process(Packet))
            {
                nClient.Disconnect();
                return;
            }

Now create a new class and replace it with:
Remember to change the password to the password you want.

    public class RemoteControl
    {
        static string Password = "12345678";
        public static bool Process(byte[] Packet)
        {
            try
            {
                string Decoded = Encoding.ASCII.GetString(Packet);
                string[] Cmd = Decoded.Split('~');

                if (Cmd[0] == "ServerCMD")
                {
                    if (Cmd[1] == Password)
                    {
                        switch (Cmd[2])
                        {
                            case "/restart":
                                {
                                    System.Diagnostics.Process.Start("ConquerServer_v2.exe");
                                    Environment.Exit(0);
                                    return true;
                                }
                            case "/close":
                                {
                                    foreach (System.Diagnostics.Process process in System.Diagnostics.Process.GetProcessesByName(Cmd[3]))
                                        process.Kill();

                                    return true;
                                }
                        }
                    }
                    else
                        return true;//We return true for disconnection
                }

                return false;
            }
            catch { return false; }
        }
    }

It can be done very different and I'm sure this is not an efficient way to do it, but this is how I would do it. You can use it to eg. Restart your server extern, manage database etc. You would have to code the functions etc. your self.

[|NeoX]

I used to do such a thing in the past using the Co2 Protocoll This one looks easy to exploit...

[Syst3m_W1z4rd]

Originally Posted by |NeoX

I used to do such a thing in the past using the Co2 Protocoll This one looks easy to exploit...

It was more an example, peoples could use encryptions etc., but the problem exploting using it would be guessing the password, since it's serverside, but you could always bruteforce it, if it's too easy, but that's how it is with everything

[pro4never]

If someone was going to do something like this I'd really recommend encryption (obviously) plus using a custom client program to handle the packets. That way you only keep the program that handles that stuff in the hands of a couple people and without it to help them guess packet structures/encryption it will be **** near impossible for them to crack your remote access.

Lets face it... writing a super basic program to send some structured packets with a basic layer of encryption is not very difficult to do and would allow so many different admin functions for the end user. Hell you could write it into a basic web server and integrate with the website + admin panel. Could do some really sexy stuff with this concept but ofc few people on epvp have the time, knowledge or desire to write such a system.

[_DreadNought_]

Pro4Never.

Asp.net

[Syst3m_W1z4rd]

Originally Posted by _DreadNought_

Pro4Never.

Asp.net

^