If you have an ssh-agent up and running it is very irritating to add the ssh-key "again" if you have done before during the startup using ssh-askpass.

I would use the same ssh-key to access some remote systems as I have on my system (NFS mounted homedirectory). So the key is already loaded and I guess we could make use of the ssh-agent instead of saving the ssh-key in memory.

I am thinking along the lines of: ​http://twistedmatrix.com/documents/8.2.0/api/twisted.conch.ssh.agent.SSHAgentClient.html

Split from #168 - see there for details.

What we want is the ability for the user connected to the session to decide what to do with requests (within that session) for opening new files and URLs. Give them 3 options:

• open them as normal (application used will be part of the same session as the one that launched it) - current behaviour
• open them in a new session (create a new session and attach it automatically)
• open them on the client (only valid for URLs, files would have to be copied over first which is a lot more tricky!)

Some of the exception handling is broken (references non-existent attributes or not using all arguments in string formatting). Attached patch fixes both I found.