@demobox, I've run the live tests again with different combinations of sshj and
bouncycastle:
* [x] **sshj 0.8.1 / bouncycastle 1.46**
testAScriptExecutionAfterBootWithBasicTemplate(org.jclouds.digitalocean.compute.DigitalOceanComputeServiceLiveTest)
_succeeded_
* [x] **sshj 0.8.1 / bouncycastle 1.49**
testAScriptExecutionAfterBootWithBasicTemplate(org.jclouds.digitalocean.compute.DigitalOceanComputeServiceLiveTest)
_succeeded_
* [x] **sshj 0.9.0 / bouncycastle 1.49**
testAScriptExecutionAfterBootWithBasicTemplate(org.jclouds.digitalocean.compute.DigitalOceanComputeServiceLiveTest)
_failed_
* [ ] **sshj 0.9.0 / bouncycastle 1.46**
Haven't tested it, but I don't think it is a good idea as sshj 0.9.0 dends on
BC 1.49 and forcing it to an earlier version does not seema good idea.
So it seems that sshj 0.8.1 works with both, BC 1.46 and 1.49, but sshj 0.9.0
presents the connection issue. With this results in mind, I'd suggest **not**
upgrading the sshj dependency but configuring the following in the
*jclouds-sshj* driver to make sure it uses BC 1.49:
```xml
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcpkix-jdk15on</artifactId>
<version>1.49</version>
<exclusions>
<exclusion>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk15on</artifactId>
</exclusion>
</exclusions>
</dependency>
```
WDYT?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34146391