under osx not using ssh-agent about mole HOT 4 CLOSED

Could you provide the mole's output with the -v flag set?

from mole.

ssh-add -l
4096 SHA256:xxxxx /Users/martinmenhart/.ssh/id_rsa (RSA)
3072 SHA256:xxxxx /Users/martinmenhart/.ssh/id_dsa (DSA)

martinmenhart at MartinMsMBP-2 in ~
$ cat ~/.mole.conf
[tunnels]
[tunnels.rbproxy01]
local = [":8991"]
remote = [":8998"]
server = "redhybcprxp01"
key = ""
verbose = true
help = false
version = false
detach = false

martinmenhart at MartinMsMBP-2 in ~
$ mole -start rbproxy01 -v
DEBU[0000] cli options options="[local=:8991, remote=:8998, server=SOMESERVER, key=, verbose=true, help=false, version=false, detach=false]"
DEBU[0000] using ssh config file from: /Users/martinmenhart/.ssh/config
The key provided is secured by a password. Please provide it below:
Password:

martinmenhart at MartinMsMBP-2 in ~
$ ssh SOMESERVER date
Fri Oct 4 14:22:24 CEST 2019

from mole.

Thank, @saltmaster-at .

Mole does not include support for ssh-agent yet.

We could leverage the ssh-agent client from x/crypto/ssh to implement this feature.

from mole.

I'd like to take shot at this. I've got some preliminary changes that work, but need some cleanup.

Right now I'm just using whatever socket SSH_AUTH_SOCK points at. I don't really think this needs to be configurable as that is the environment variable set when starting ssh-agent traditionally (eval $(ssh-agent)).

from mole.