Server
Blitz3D Forums/Blitz3D Beginners Area/Server
| ||
| OK I have a program I have made to act as a server for one of my games! I have got it to work fine but the problem I ma faced with is how do I run it wothout getting hacked as I can only have one broadband connection! I have a spare computer but it is over a network! Ohh I don't like getting haked an I jsut know A NORMAL FIRE WALL won't work! |
| ||
| Hacked? How exactly do you mean this? IF you are afraid someone could use your Game Client and get connected - you could use Tickets: The first client will get a Ticket, a randomly choosen Number or Code. He will then use this to identify himself each time Data is requested or sent to the server. If a Ticket is in Use then other connections will not be accepted (Max. Number of Tickets in Use is 1, no new Tickets are given away). Other Tickets than the one the server generated - of course - will not be accepted as well. An other, maybe easier way would be to use the Client IP as an authorisation to deny further connections. Both will not protect you from connection-ATTEMPTS - this could only do a firewall. So somebody could still DOS you with Connection-Attempts. |
| ||
| Always wanted to know how this hacking actually works, I mean, how can a serie of data work as anything but the numbers you can read it as? |
| ||
| NO I mean I have made a server for a game I have made and I want pepole to connect to it!! I want to run it so pepole can connect!! Yet I don't want to get hacked and really I don't want to run it on my comp! |
| ||
| Always wanted to know how this hacking actually works, I mean, how can a serie of data work as anything but the numbers you can read it as? Frequently by bugs in the code reading those data. If you give it some unexpected data it can cause errors and cause all sorts of problems. It might even run some of the data through the CPU and execute it. |
| ||
| When your using CreateTcpServer(), you CANNOT get hacked. You control all data transfer by reading the stream, therefore it is totally secure proof. They can't acces your operating system, they cannot download or upload any files, they can't do anything. The only security issues are those of windows. |
| ||
| There is no such thing as a totally secure system. A clever person could work out a way to cause a buffer overflow (or whatever else they need to do), and then send their own commands to a system. |
| ||
| Some potentially useful information here |
| ||
| well when i finish my mud project, maybe i'll offer 100 dollars to the first person who can hack me. |
| ||
| The problem with running a game "server" is that it must reside OUTSIDE your firewall for people on the outside to be able to access it freely (which is what you want them to do). This means it's open to any kind of "attack" that anyone may want to try. If you're running a hardware firewall, see if it has an option to configure a "DeMilitarized Zone" or "DMZ". This will allow you to put a computer on your network outside the protection of the firewall and still leave it connected to your network. You can control when it's exposed to the outside world usually, so people can only try to connect when you're "open for business", and not at other times. Unfortunately, the computer you place in the "DMZ" WILL be vunerable to any "hack attacks" that come along, but at least the rest of your network will stay secure. It's best to leave that system as simple as possible so it can be restored easily if necessary, and naturally you wouldn't keep anything important or valuable on it. This is usually the only way to be able to give the world access to your network for games while still keeping it as safe as possible. (For example, the $40 SMC7004VBR router I just installed lets me place one or more systems outside the wall if I want to run a game server. I haven't done it yet, but if I do, I'll know the rest of my network will still be safe.) |
   |