laforge49 / jasocket Goto Github PK

When doing a setPassword or changePassword via ssh, the password is accessible via the history. Shouldn't be too hard to fix. It is a matter of making a minor change to how jline is integrated with JASocket.

When a host is disconnected/reconnected from the network, the node on that host does not reconnect to the cluster.

The IntCon class, which provides ^C interception for IntCon, uses sun.misc.Signal and sun.misc.SignalHandler. These may not be supported on other JDKs or in future releases.

If this poses a problem, create your own alternative to IntCon. The ConsoleApp API was designed to make this easy.

The problem is that many IDEs do not yet support java.io.Console, which is used for entering a password.

This does not seem to be a pressing issue and at some point the IDEs will be fixed.

Combining the to and halt commands results in the sending node locking up.

On the destination node, it was also found that the to actor pends when doing a jid copy until the halt actor returns control, despite the halt actor having its own async mailbox.

node exits or hangs when a node on another host halts.

To generalize this, a user interrupt should be sent to the command actor. And server commands should be converted to command actors. The command actor then has an option of returning partial results. But if there is a second user interrupt, then the sshServer abandons the command actor.

Note that this has implications for both to and server commands.