> this is my client need, he want private FTPS server so only customer that > have the client program can access his server, and block all public ftp > client, the project is about remote updating application using FTPS server > and client part is component that I will code to add to another application > so it get update from server, so it don't need the server send PK, the idea > is that the client send the one coded inside to the server after the hello > negotiation so the server valid only his trusted client and denied all > public ftp client.
To complement/summarize Arno and Angus answers, I would implement your requiredments either by: 1) Using a client certificate, which is already implemented in SSL. 2) Adding a simple custom command which would be mandatory for user to use. Commercial FTPS client will not implement that command and would have difficulties in executing it. The passphrase associated with the certificate could be hardcoded in your application. -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be