activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQCPP-495) CPP clients support IPv6 and ssl transportation through http/socks(4or5) proxy
Date Tue, 02 Jul 2013 14:21:20 GMT

     [ https://issues.apache.org/jira/browse/AMQCPP-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish closed AMQCPP-495.
-------------------------------

    Resolution: Unresolved

v3.4.x is no longer maintained.  
                
> CPP clients support IPv6 and ssl transportation through http/socks(4or5) proxy
> ------------------------------------------------------------------------------
>
>                 Key: AMQCPP-495
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-495
>             Project: ActiveMQ C++ Client
>          Issue Type: New Feature
>          Components: Decaf, Transports
>    Affects Versions: 3.4.5
>            Reporter: Kimi Wu
>            Assignee: Timothy Bish
>            Priority: Minor
>         Attachments: ipv6_proxy.patch
>
>
> 1. ActiveMQ broker supports IPv6 protocol. But current ActiveMQ-CPP clients don't. My
partner and I modified ActiveMQ-CPP 3.4.5 to support IPv6.
> 2. In some cases activemq-cpp clients have to connect to activemq through a proxy. But
current tcp/ssl transport does not provide this functionality.
> My partner and I modified ActiveMQ-CPP 3.4.5 to enable SSL transport to support http/socks4/socks5
proxy.
> 3. In some cases the certification of ActiveMQ broker can't be regenerated. However,
ActiveMQ-CPP clients need the "commonName" field in the certification matches the server host
name. My partner and I modified ActiveMQ-CPP 3.4.5 to overwrite the server host name.
> *******************************************
> What is changed:
> A local patched ActiveMQ-CPP, based on 3.4.5, 
> which supports IPv6 and Http / Socks 4 / Socks 5 proxy for SSL transport.
> Proxy usgae:
> To enable proxy for SSL transport, use these system properties 
> property comments
> ----------------------------------------------------------------
> decaf.net.ssl.proxyType     values:http/socks4/socks5
> decaf.net.ssl.proxyHost     proxy address
> decaf.net.ssl.proxyPort     proxy port
> decaf.net.ssl.proxyUser     proxy user name
> decaf.net.ssl.proxyPassword proxy password
> Overwriting server host name usage:
> To overwrite the field, use these system properties 
> property comments
> ----------------------------------------------------------------
> decaf.net.ssl.serverName    the name matched "CommonName" field
> source: ipv6_proxy.patch
> *******************************************

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message