🚀 go-pugleaf

Hi Emmanuel,

I do not use 'SocketServer', so I cannot help you there. I use 
TWebConnection. The method I use to hide servers from being exposed is 
to configure IIS to require SSL for the CGI directory - the certificates 
I use are generated by OpenSSL. Unless the client has installed the 
valid certificates, they will not be able to connect to and/or view 
available servers (because without the certificates installed in the 
correct certificate store, httpsrvr.dll is not accessible).

This is not fool-proof though - users with a little know-how will be 
able to save these SSL certificates and install them onto other PC's. 
This is not a problem for the majority of my projects, as it doesn't 
matter if Joe Public can see what appservers are running on a particular 
box, they still won't be able to access the data without valid 
credentials. For my projects that are sensitive (where the appservers 
are not on the same LAN as the client apps), my clients use VPN's.

As a suggestion, maybe you could look at 'tunneling' using something 
like PuTTY (again, this is not something I have tried but intend on 
looking into once I find the time). If you do get it working, it may 
only afford you the same kind of result I have by forcing SSL on the CGI 
folder containing httprsrvr.dll. It may, however, prevent most users 
from viewing your appservers.

Good luck, and if you do make a break-through, please let me know the 
results (I will do the same once I get around to looking at tunneling 
and ScktSrvr.exe)

Regards,
Syd.


Emmanuel wrote:
> No Help???
> "Emmanuel" <emmanuel@erphk.com> д���ʼ�
> news:41d3445e@newsgroups.borland.com...
> 
>>How to let the cracker cannot get the information or data from the Socket
>>Server
>>I find that just know the Socket Server's IP and port, everybody can know
>>all the ServerName in Socket Server  and know all the ProviderName in
> 
> every
> 
>>ServerName
>>Can the server of the application discount any client?
>>
>>Thank you
>>Emmanuel
>>
>>
> 
> 
>