[
https://issues.apache.org/activemq/browse/AMQ-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58401#action_58401
]
Phil Pickett commented on AMQ-2384:
-----------------------------------
Actually, I looked at the test case and modified my transport connector config
in what I thought was the way to enable the ciphers I wanted with:
<transportConnector name="openwire"
uri="ssl://0.0.0.0:61616?transport.enabledCipherSuites=SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA,SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA"/>
It looks to me when running an SSL scan that this is not being set. When I run
a PCI scan against a similarly configured Tomcat instance I see the weak
ciphers are disabled.
> The activeMQ port supports low and medium strength ciphers
> -----------------------------------------------------------
>
> Key: AMQ-2384
> URL: https://issues.apache.org/activemq/browse/AMQ-2384
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: 5.2.0
> Environment: We are running the ActiveMQ 5.2.0 over a SLES 11 64 bit
> machine. In the configuration file activemq.xml there is no way to specify
> the supported ciphers.
> Reporter: Shrisha Chandrashekar
> Fix For: 5.4.0
>
> Attachments: setSslSocketOptions.patch
>
>
> On running a Tenable nessus scan against the machine where ActiveMQ is
> running, we see that the port 61616 , the TCP connector port accepts Low and
> Medium strength ciphers by default. This may be a security risk and therefore
> we need a way to specify which ciphers to support.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
