You have to execute that code in another thread so you don’t hang the UI thread is what that exception means. If the UI thread is executing a network call it can’t repaint the UI so your users sees a frozen UI that doesn’t respond to them while the app is waiting on the network … Read more
Try this: JSch jsch = new JSch(); try { Session session = jsch.getSession(“root”, “192.168.0.1”, 22); java.util.Properties config = new java.util.Properties(); config.put(“StrictHostKeyChecking”, “no”); session.setConfig(config); session.connect(); String command = “lsof -i :80”; Channel channel = session.openChannel(“exec”); ((ChannelExec) channel).setCommand(command); channel.setInputStream(null); ((ChannelExec) channel).setErrStream(System.err); InputStream in = channel.getInputStream(); channel.connect(); byte[] tmp = new byte[1024]; while (true) { while (in.available() > … Read more
I ended up using Jsch- it was pretty straightforward, and seemed to scale up pretty well (I was grabbing a few thousand files every few minutes).
Have a look at Runtime.exec() Javadoc Process p = Runtime.getRuntime().exec(“ssh myhost”); PrintStream out = new PrintStream(p.getOutputStream()); BufferedReader in = new BufferedReader(new InputStreamReader(p.getInputStream())); out.println(“ls -l /home/me”); while (in.ready()) { String s = in.readLine(); System.out.println(s); } out.println(“exit”); p.waitFor();
An overview about the differences and similarities between these streams you can find at »Shell, Exec or Subsystem Channel« in the JSch wiki. Here some details for your use case. In the exec channel, the commands come from the command string you did give with setCommand(). The SSH server will pass them at once to … Read more
It is possible. Have a look at JSch.addIdentity(…) This allows you to use key either as byte array or to read it from file. import com.jcraft.jsch.Channel; import com.jcraft.jsch.ChannelSftp; import com.jcraft.jsch.JSch; import com.jcraft.jsch.Session; public class UserAuthPubKey { public static void main(String[] arg) { try { JSch jsch = new JSch(); String user = “tjill”; String host … Read more
There are a couple of places that SSH clients and servers try and agree on a common implementation. Two I know of are encryption and compression. The server and client produce a list of available options and then the best available option in both lists is chosen. If there is no acceptable option in the … Read more
My understanding is that you want to access a mysql server running on a remote machine and listening on let’s say port 3306 through a SSH tunnel. To create such a tunnel from port 1234 on your local machine to port 3306 on a remote machine using the command line ssh client, you would type … Read more
As you can see, the server offers these ciphers: INFO: kex: server: aes256-cbc,aes192-cbc But JSch accepts only these: INFO: kex: client: aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc There’s no common cipher to choose from. Note that JSch does support both aes256-cbc and aes192-cbc, but requires JCE (Java Cryptography Extension) to allow them. You probably do not have JCE, so these … Read more