Re: http://www.vbdotnetforums.com/net-sockets/22844-how-listen-tcp-port-broadcast.html. Now....how would you make this more secure?
I have a small app we use for computer maintenance, inventory, user backups, etc. I wanted to add the ability to send some commands through the network and also to pop up network messages. Got the messaging part done on a random UDP port. But what would prevent someone form just sending garbage to this UDP port and my program taking that garbage and putting it into a message box (that's all I'm doing currently).
For the time being I check the subnet they are on and if it's in our list of subnets it enables the listener thread otherwise it simply doesn't run it so that's relatively secure. How can I go a step further with a simple UDP broadcast? Make sure the first xx characters are some type of passcode and then do something?
-Allan
I have a small app we use for computer maintenance, inventory, user backups, etc. I wanted to add the ability to send some commands through the network and also to pop up network messages. Got the messaging part done on a random UDP port. But what would prevent someone form just sending garbage to this UDP port and my program taking that garbage and putting it into a message box (that's all I'm doing currently).
For the time being I check the subnet they are on and if it's in our list of subnets it enables the listener thread otherwise it simply doesn't run it so that's relatively secure. How can I go a step further with a simple UDP broadcast? Make sure the first xx characters are some type of passcode and then do something?
-Allan
Last edited: