[
https://issues.apache.org/jira/browse/KARAF-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956217#comment-14956217
]
Freeman Fang commented on KARAF-4062:
-------------------------------------
This is caused by the sshd 0.14 need use bcprov as the security provider to
workaround the jdk bug[1].
And we can see this problem when use sshd 0.14 and BouncyCastle 1.52 together.
The fix could be that we ship the BouncyCastle with Karaf kit and explicitly
let the client to use the BouncyCastle as security provider, but I'm not sure
if we can ship BouncyCastle in Karaf.
And another way to fix this is we can specify the keyExchangeFactory for the
client instead of the default one
[1]http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6521495
> Karaf client does now work after installing BouncyCastle
> --------------------------------------------------------
>
> Key: KARAF-4062
> URL: https://issues.apache.org/jira/browse/KARAF-4062
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 4.0.2
> Environment: OS X, Windows
> Reporter: Pavlo Vasylchenko
> Assignee: Freeman Fang
> Fix For: 4.0.3
>
>
> Karaf client throws:
> " Exception caught
> java.security.InvalidAlgorithmParameterException: Prime size must be multiple
> of 64, and can only ra
> nge from 512 to 2048 (inclusive)
> at
> com.sun.crypto.provider.DHKeyPairGenerator.initialize(DHKeyPairGenerator.java:120)"
> after installing mvn:org.bouncycastle/bcprov-jdk15on/1.52 into container
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
