it would be very helpfull to set the interface or ip-address to listen on at a multi homed server.
Spearated private and public lan. Listen only on the private lan interface.
After having installed the CapeSoft e-mail server I found that it had a very nice feature: "Unless the incoming TCP/IP address matched the value ranges listed below, they will be rejected." This simple interface allowed the e-mail server to only accept from those places you knew were good locations. The default locations are only those for a local area network (ie: 192.168.0.0-192.168.*.*, etc...). This would be a simple, yet ideal way to ensure that if someone were to try to log in to a system running TightVNC that they'd have to fall into the trusted network. All attempts to connect from outside of the trusted network would receive a message which the user could set. (Default could be something as simple as "All connections from your TCP/IP address are disabled".)
So my suggestion is to make TightVNC have a TCP/IP table that has a range of default addresses in it and allow the user to modify that table. TightVNC would only accept incoming requests from this list of TCP/IP addresses and no other. It would also display a message as defined by the user back to the person on the other end (if possible). Basically what the original person said only I'm expanding upon it and giving another piece of software that can be downloaded and looked at as an example.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
bind to an ip you mean. thats what i want but for a vpn.
Logged In: YES
user_id=1125864
Originator: NO
I thought I'd make a comment here about this. :-)
After having installed the CapeSoft e-mail server I found that it had a very nice feature: "Unless the incoming TCP/IP address matched the value ranges listed below, they will be rejected." This simple interface allowed the e-mail server to only accept from those places you knew were good locations. The default locations are only those for a local area network (ie: 192.168.0.0-192.168.*.*, etc...). This would be a simple, yet ideal way to ensure that if someone were to try to log in to a system running TightVNC that they'd have to fall into the trusted network. All attempts to connect from outside of the trusted network would receive a message which the user could set. (Default could be something as simple as "All connections from your TCP/IP address are disabled".)
So my suggestion is to make TightVNC have a TCP/IP table that has a range of default addresses in it and allow the user to modify that table. TightVNC would only accept incoming requests from this list of TCP/IP addresses and no other. It would also display a message as defined by the user back to the person on the other end (if possible). Basically what the original person said only I'm expanding upon it and giving another piece of software that can be downloaded and looked at as an example.