<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:14:59 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[NETCONF-421] SSH issue: unable to open SSH session due to invalid crypto configuration</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-421</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;I&apos;m using the Opendaylight Boron Distribution and I have got some problems to connect it to a NETCONF server embedded in a ConfD simulator using SSH. This issue seems to appear from Boron SR2 release and seems not have been resolved yet.&lt;/p&gt;

&lt;p&gt;An Invalid Algorithm Parameter Exception is raised when trying to connect Opendaylight to a NETCONF device and OpenDaylight fails to open an SSH session with the device :&lt;/p&gt;

&lt;p&gt;2017-05-03 16:40:53,927 | INFO | 3]-nio2-thread-2 | ClientSessionImpl | 30 - org.apache.sshd.core - 0.14.0 | Server version string: SSH-2.0-ConfD-6.0 2017-05-03 16:40:53,928 | WARN | 3]-nio2-thread-7 | ClientSessionImpl | 30 - org.apache.sshd.core - 0.14.0 | Exception caught java.security.InvalidAlgorithmParameterException: DH key size must be multiple of 64, and can only range from 512 to 2048 (inclusive). The specific key size 4096 is not supported&lt;/p&gt;

&lt;p&gt;2017-05-03 16:40:53,929 | WARN | 3]-nio2-thread-7 | AsyncSshHandler | 217 - org.opendaylight.netconf.netty-util - 1.2.0.SNAPSHOT | Unable to setup SSH connection on channel: &lt;span class=&quot;error&quot;&gt;&amp;#91;id: 0x19ec738f&amp;#93;&lt;/span&gt; org.apache.sshd.common.SshException: Session is closed&lt;/p&gt;

&lt;p&gt;One workaround is to locate mina sshd jar in Opendaylight distribution&#8217;s system folder. From Boron release, it is :&lt;br/&gt;
&#8226;Go to : &lt;span class=&quot;error&quot;&gt;&amp;#91;ODLprojectfolder&amp;#93;&lt;/span&gt;/karaf/target/assembly/system/org/apache/sshd/sshd-core/0.14.0/sshd-core-0.14.0.jar&lt;br/&gt;
&#8226;Open the jar file, locate META-INF/MANIFEST.MF file and edit the file&lt;br/&gt;
&#8226;Find org.bouncycastle.openssl;version=&#8221;[1.51,2)&#8221;;resolution:=optional (at the end of the MANIFEST.MF file) and then delete ;resolution:=optional&lt;/p&gt;

&lt;p&gt;Note that this must be done after the project&apos;s compilation, but before Karaf is started for the first time.&lt;/p&gt;

&lt;p&gt;Does anyone know if and when this issue will be fixed ?&lt;/p&gt;

&lt;p&gt;Thanks, Christophe&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="21434">NETCONF-421</key>
            <summary>SSH issue: unable to open SSH session due to invalid crypto configuration</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="christophe.betoule@orange.com">ChristopheBetoule</reporter>
                        <labels>
                    </labels>
                <created>Fri, 12 May 2017 10:02:00 +0000</created>
                <updated>Fri, 15 Mar 2019 22:22:41 +0000</updated>
                            <resolved>Fri, 7 Jul 2017 16:31:55 +0000</resolved>
                                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="40080" author="tcere" created="Wed, 28 Jun 2017 12:51:50 +0000"  >&lt;p&gt;This shouldbe  fixed by adding bouncy castle to startup bundles&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/58133/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/58133/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="40081" author="gwenael.lambrouin@b-com.com" created="Fri, 7 Jul 2017 16:31:55 +0000"  >&lt;p&gt;The fix is merged on master (nitrogen). It cannot be cherry-picked directly for stable/carbon or stable/boron because it is based on karaf4.&lt;/p&gt;

&lt;p&gt;However, in essence, it works for me on stable/carbon: after the karaf build, if I edit karaf/target/assembly/etc/startup.properties and append the line:&lt;/p&gt;

&lt;p&gt;mvn\:org.bouncycastle/bcprov-jdk15on/1.56 = 14&lt;/p&gt;

&lt;p&gt;then sshd-core will use bcprov right after the karaf startup, and the netconf/ssh connection works (in my case: with netconf-testtool and a Juniper MX5 routers running JunOS 14.2R1.9).&lt;/p&gt;

&lt;p&gt;Now, the question is: is it possible to automate that during the build of the karaf distribution? I tried this in my karaf/pom.xml, but this did not work (and did not cause a build error either):&lt;/p&gt;

&lt;p&gt;&amp;lt;build&amp;gt;&lt;br/&gt;
  &amp;lt;plugins&amp;gt;&lt;br/&gt;
  &amp;lt;!-- ... --&amp;gt;&lt;br/&gt;
    &amp;lt;plugin&amp;gt;&lt;br/&gt;
      &amp;lt;groupId&amp;gt;org.apache.karaf.tooling&amp;lt;/groupId&amp;gt;&lt;br/&gt;
      &amp;lt;artifactId&amp;gt;karaf-maven-plugin&amp;lt;/artifactId&amp;gt;&lt;br/&gt;
      &amp;lt;configuration&amp;gt;&lt;br/&gt;
        &amp;lt;startupFeatures&amp;gt;&lt;br/&gt;
          &amp;lt;feature&amp;gt;bcprov-jdk15on&amp;lt;/feature&amp;gt;&lt;br/&gt;
        &amp;lt;/startupFeatures&amp;gt;&lt;br/&gt;
      &amp;lt;/configuration&amp;gt;&lt;br/&gt;
     &amp;lt;/plugin&amp;gt;&lt;br/&gt;
  &amp;lt;/plugins&amp;gt;&lt;br/&gt;
&amp;lt;/build&amp;gt;&lt;/p&gt;

&lt;p&gt;Besides, should not we also add bcpkix to startup.properties? During my investigations, I observed that sshd-core used osgi packages in bcpkix. Seems unnecessary for the present issue, but could lead to other problems later...&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>8431</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=8431]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i01yfr:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>