Re: [Quickfix-users] Does QuickFix support SSL

[Eric G. <EGu...@FF...>]

Oren:

I have looked at OpenSSL, and implementation seems fairly straight 
forward. Alas, I had hoped this was already done. 

I'll try to get my boss to OK it. If so, I'd be willing to share when I'm 
done.

If I read your source properly, I should only have to subclass 
SocketConnection and ThreadedSocketConnection to actually support 
transport, is that right? Seems that SocketAcceptor and SocketInitiator 
should probably be subclassed as well to allow for initialization settings 
and to provide a clean implementation. Would you agree? Come to think of 
it, SocketConnector would probably make sense too...

Guidance would be appreciated, as I've only spent a day or so looking at 
your stuff.

Eric Gufford
212-681-3130
egu...@ff...




Oren Miller <ore...@ya...>
12/10/2003 05:00 PM

 
        To:     Eric Gufford <EGu...@FF...>, qui...@li...
        cc: 
        bcc: 
        Subject:        Re: [Quickfix-users] Does QuickFix support SSL


Currently no.  We do have plans to inegrate openssl
(http://www.openssl.org/) into QuickFIX, but have not
yet done so.  I havn't looked at the library very
closely so I'm not sure how big a task it would be.
(if someone has already done this please let us know!)

--- Eric Gufford <EGu...@FF...> wrote:
> Does QuickFix support SSL connections to
> counterparties? We have a venue 
> that supports FIX, but uses SSL and no FIX
> encryption.
> 
> Eric Gufford
> 212-681-3130
> egu...@ff...
> 
>
**********************************************************************
> This e-mail message is intended solely for the use
> of the addressee. The message
>  may contain information that is privileged and
> confidential.  Disclosure to
> anyone other than the intended recipient is
> prohibited. If you are not the
> intended recipient, please do not disseminate,
> distribute or copy this
> communication, by e-mail or otherwise. Instead,
> please notify us immediately by
> return e-mail (including the original message with
> your reply) and then delete
> and discard all copies of the message.
> We have taken precautions to minimize the risk of
> transmitting software viruses
>  but nevertheless advise you to carry out your own
> virus checks on any
> attachment to  this  message.  We  accept  no 
> liability  for any loss or damage
>  caused by software viruses.
>
**********************************************************************
> 
> 


__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/




**********************************************************************
This e-mail message is intended solely for the use of the addressee. The message
 may contain information that is privileged and confidential.  Disclosure to
anyone other than the intended recipient is prohibited. If you are not the
intended recipient, please do not disseminate, distribute or copy this
communication, by e-mail or otherwise. Instead, please notify us immediately by
return e-mail (including the original message with your reply) and then delete
and discard all copies of the message.
We have taken precautions to minimize the risk of transmitting software viruses
 but nevertheless advise you to carry out your own virus checks on any
attachment to  this  message.  We  accept  no  liability  for any loss or damage
 caused by software viruses.
**********************************************************************