> Hi Viktor! > > An remote client connects (command line app or not) on hbnetiosrv he > needs must know the IP, port and password on our server. I say that > already exists at this point a certain level of security (even though > very little) in this respect.
Yes, as you say very little. These things are not that much of a problem if the server is running inside a LAN protected from the outside (typical for hbnetiosrv), but for any server that gets opened to the internet, it's highly unsafe. Remember that now we have only _one_ password which protects the only one data connection that exist, and using the same password for data connection and admin connection is already a big security problem, even for a local network with many users. It can be solved, but it needs effort. > Now I understand your point of view and you're right. But I believe we > dont have to worry about this right now. If we will be lucky to have GTNET in the future, at least I'll have to deal with these (at least if I need the comfort of built-in remote control). Since GTNET will happily run via slow internet connections, too. BTW, we will also need to deal with this if we want to convert (= run) either hbnetiosrv or hbgtsrv to/as a daemon or Windows service. This is the only way to control such "headless" setups. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
