[
https://issues.apache.org/activemq/browse/AMQCPP-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Teemu Torma updated AMQCPP-140:
-------------------------------
Attachment: amqcpp-ssl.patch3
Version 3 of the patch.
- autoconf --with-ssl and --with-openssl (adapted from apr-util)
- Probably solves the 64-bit windows issue. It no longer uses SSL_use_fd but
the underlying mechanism using BIO socket interface. We haven't figured the
proper way for windows configuration, the user has to add manually the
preprocessor directives and libraries.
- Proper openssl setup for multithreading.
> 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.patch3
>
>
> 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.
