Private key required when ssh-agent already populated about upterm HOT 7 CLOSED

Another option from discussions in #72 is maybe we could create temporary public/private keys when running upterm host. I'm not sure the client ever cares what the private key from the server to upterm connection host is. Maybe I'm still understanding what the private key is actually used for on the host.

from upterm.

upterm should already read keys from ssh-agent first then fall back to key files:

from upterm.

My use case is on temporary hosts that don't have ssh keys or ssh-agent available. In that case it would be great if there were an easier way to create the ssh tunnel connection

from upterm.

@rothgar upterm starts an sshd server on the host and the ssh keys are used to establish a secured tunnel between the host and the uptermd server: https://github.com/owenthereal/upterm#how-it-works. There are tools like ssh-keygen to generate keys already, are you looking for upterm to generate the keys for you instead?

from upterm.

Yes, automatically generating a key (or having a flag to auto generate a key) is what I was thinking. I know users can create ssh keys but in the case that the machine/user doesn't have a key it would be nice to automatically generate a temporary key for the initial tunnel.

This would be especially useful on temporary cloud instances or from inside containers.

from upterm.

The problem is, the --private-key argument is mandatory, and I don't have one since my private key is not physically accessible (it's in my keepass2 vault)

from upterm.

Thanks! I'll try this soon!

from upterm.