Greetings, We have a proprietary client/server application that now has need to be offered to clients across the Internet. Unfortunately this particular application does not have any provision for security (e.g. encryption, etc.). What I have done is to add SSL support to the widely available redir() package. This seems to work, at least with the tests performed thus far... POP3, SMTP, custom servers, etc. There still are a few issues to work out (mostly logistical on our part) but it seems to work. The full scenario is this: Client gets a SSLredir() application to run on their local workstation. They then point the "plain text" client to a local port on their machine. The SSLredir() then sends the data, SSL-style, to another SSLredir running on our server/firewall/whatever. My questions are this: * Is there any problem with this kind of approach? * Anything in particular that we should keep in mind? * Anything that we might have missed? * Are we re-inventing the wheel? Thanks in advance, - Bennett P.S. For those who might ask, the SSLredir() application for Windows is one of the pieces that we have yet to develop as the client application is Windows based. - [To unsubscribe, send mail to [EMAIL PROTECTED] with "unsubscribe firewalls" in the body of the message.]
