Craig wrote:
> Well, does it need to be actual SSL, or would other encryption be ok?
> There is lots more choices for encryption if you dont need SSL.
>
>
> "D-Fan" <D-Fan@antispam.com> wrote in message
> news:47996f56$1@newsgroups.borland.com...
>> Remy Lebeau (TeamB) wrote:
>>> "D-Fan" <D-Fan@antispam.com> wrote in message
>>> news:47993fe9$1@newsgroups.borland.com...
>>>
>>>> We have an application that uses tcp/ip to communicate between
>>>> computers on the internet. We establish a socket connection and
>>>> then we send text across the socket to the receiving PC. We want
>>>> to secure this communication using SSL. What is the best way to
>>>> use SSL to communicate between these PC's?
>>> That depends on what you are using for your TCP coding to begin with.
> Are
>>> you using straight winsock API function calls, or are you using a
>>> third-party wrapper library/component?
>>>
>>>
>>> Gambit
>>>
>>>
>> The winsock api. We need to understand the client and server side setup
>> beyond generating the keys. Can we assign our own port, how do we setup
>> SSL, what is the impact on our existing data stream process?
>
>
Unfortunately it has to be SSL because the recipient is an SSL server.
I am wondering if i can use Stunnel to communicate with SSL. This will
let us separate the SSL from our core program.
