[
https://issues.apache.org/jira/browse/CAMEL-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234597#comment-14234597
]
ASF GitHub Bot commented on CAMEL-8123:
---------------------------------------
GitHub user peterberkman opened a pull request:
https://github.com/apache/camel/pull/349
Camel 2.13.x Correct TLS Handshake
fixes: https://issues.apache.org/jira/browse/CAMEL-8123
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/peterberkman/camel camel-2.13.x
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/349.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #349
----
commit 0fe18488bc237ce1d03b92dc50c0a8e62b6ebdc9
Author: peterberkman <[email protected]>
Date: 2014-12-04T20:29:45Z
Fixes #CAMEL-8123: Consumer should NOT use ClientMode for TLS
commit e446b90315534ca9a6ed8a6a76e5bd3af748f012
Author: peterberkman <[email protected]>
Date: 2014-12-04T20:33:02Z
Fixes #CAMEL-8123: Producer SHOULD use ClientMode for TLS
----
> Mina2 SSL initiates handshake backwards
> ---------------------------------------
>
> Key: CAMEL-8123
> URL: https://issues.apache.org/jira/browse/CAMEL-8123
> Project: Camel
> Issue Type: Bug
> Components: camel-mina2
> Affects Versions: 2.13.3, 2.14.0
> Reporter: Justin Cozzens
>
> The Mina2Consumer and Mina2Producer are configured backwards for SSL
> handshake initiation. The consumer is trying to initiate the handshake rather
> than the producer. You can see this by setting up a SSL enabled consuming
> route and telnet to the port, you will immediately get some data sent from
> the server to the client rather than the server waiting on the client to
> initiate the handshake.
> The issue is Mina2Consumer:160, it is setting UseClientMode to true, it
> should be false. Mina2Producer line 313 needs to also change to the following:
> SslFilter filter = new
> SslFilter(configuration.getSslContextParameters().createSSLContext(),
> configuration.isAutoStartTls());
> filter.setUseClientMode(true);
> connector.getFilterChain().addFirst("sslFilter", filter);
> As far as I can tell this has been a bug since this component was introduced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
