[
https://issues.apache.org/activemq/browse/AMQCPP-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40450
]
Teemu Torma commented on AMQCPP-140:
------------------------------------
I should have mentioned I have tested on Linux only. I don't even have any
windows machines, I would have to delegate that part.
By searching I don't see any other usage on windows, everything seems to be
using SSL_set_fd. We are also using omniORB which also implements ssl and
works in all platforms uses it (I used the code as a reference too whilst doing
this, I have not programmed with openssl before.)
here is something called BIO interface in openssl that could be used too, but
that does not seem to be any different in this case. That would just add yet
another abstraction layer and I feel there are already enough of them :)
If it works on windows, maybe just stick reinterpret_cast for the call.
> Add SSL transport
> -----------------
>
> Key: AMQCPP-140
> URL: https://issues.apache.org/activemq/browse/AMQCPP-140
> Project: ActiveMQ C++ Client
> Issue Type: New Feature
> Affects Versions: 2.2
> Reporter: Nathan Mittler
> Assignee: Nathan Mittler
> Fix For: 2.2
>
> Attachments: amqcpp-ssl.patch1
>
>
> Need a secure transport for activemq-cpp. Some options for ssl support:
> 1) OpenSSL - fairly robust set of ssl functions
> 2) APR - trunk has added support for ssl sockets. An attractive option,
> given that we're already starting to incorporate API in other areas.
> Should create a Java-like set of classes in decaf to add basic ssl support,
> then use those classes to make an SSLTransport in activemq-cpp.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
