[
https://issues.apache.org/activemq/browse/AMQ-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54289#action_54289
]
Shrisha Chandrashekar commented on AMQ-2384:
--------------------------------------------
Ya.. i tried specifying the ciphers as a uri parameter
"socket.enabledCipherSuites" , by using comma separated strings , seems like
this does not work. I dont think the introspection support can deal with
String[]. We want to do this at the application level rather than at the
system level so configuring the tls layer is not a good alternative. I feel we
need to provide a tag for specifying the ciphers under the <TransportConnector>
, but not sure if its the right way to do this.
> 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
>
>
> 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.
