Hi,
I confirm the issue with Boron-SR1 with different netconf devices. There is no
problem with Be-SR2.
Before the java.security.InvalidAlgorithmParameterException, I have the
following exception:
2016-11-25 12:15:07,765 | WARN | ntLoopGroup-11-1 | ChannelInitializer
| 111 -
ram
>
>
>
> *From:* Ryan Goulding [mailto:ryandgould...@gmail.com]
> *Sent:* 22 November 2016 20:30
> *To:* Vikram Darsi
> *Cc:* controller-dev@lists.opendaylight.org; netconf-dev@lists.
> opendaylight.org
> *Subject:* Re: [controller-dev] InvalidAlgorithmParameterException during
&
: [controller-dev] InvalidAlgorithmParameterException during SSH key
exchange
Hi Vikram,
I have run into this too before. You need to make sure you are using bouncy
castle JCE, which is described here [0]. Basically, even though the default
JCE + Unlimited Strength Policy + JDK8 "allows&qu
Hi Vikram,
I have run into this too before. You need to make sure you are using
bouncy castle JCE, which is described here [0]. Basically, even though the
default JCE + Unlimited Strength Policy + JDK8 "allows" for 2K DHE keys,
they do not work in Ubuntu.. no idea why. They do work in CentOS.
