[brooklyn-server] 14/28: bump sshj and other crypto versions

[he...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

heneveld pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-server.git

commit 7d4c962d9b4023c2741658c73594f723ac7f51e8
Author: Alex Heneveld <al...@cloudsoftcorp.com>
AuthorDate: Tue Nov 9 15:46:39 2021 +0000

    bump sshj and other crypto versions
    
    with notes on why they can't easily be bumped further
---
 pom.xml | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/pom.xml b/pom.xml
index af5fcd7..a211c12 100644
--- a/pom.xml
+++ b/pom.xml
@@ -138,11 +138,9 @@
         <!-- Next version of swagger requires changes to how path mapping and scanner injection are done. -->
         <swagger.version>1.6.2</swagger.version>
         <mx4j.version>3.0.1</mx4j.version>
-        <bouncycastle.version>1.67</bouncycastle.version>
-        <!-- JClouds 2.2.0 imports eddsa 0.1.0 -->
-        <eddsa.version>0.2.0</eddsa.version>
-        <!-- JClouds 2.2.0 imports ssjj 0.20.0 -->
-        <sshj.version>0.22.0</sshj.version>
+        <bouncycastle.version>1.67</bouncycastle.version>  <!-- beyond this gives asn1 errors, needs a new dep probably -->
+        <eddsa.version>0.2.0</eddsa.version>  <!-- eddsa 0.3.0 needs sun x509 -->
+        <sshj.version>0.27.0</sshj.version>  <!-- jclouds 2.4 uses 0.27; 0.32 needs eddsa 0.3.0 -->
         <!-- jzlib osgi version is 1.1.3.2, but bundle is 1.1.3_2 ; JClouds 2.2.0 pulls in 1.0.7_1 but is happy with 1.1.3.2 -->
         <jzlib.version>1.1.3_2</jzlib.version>
         <jzlib.osgi.version>1.1.3.2</jzlib.osgi.version>