sshuttle does not seem to be parsing SSH Config file in macOS X 10.12

[Jamie Peloquin]

Hi

Since updating to macOS 10.12, it seems as if sshuttle is no longer able to either parse or read my .ssh/config file.

For example:

sudo sshuttle -Hv --remote my-bastion-host 10.1.1.1/32

now fails with:

ssh: Could not resolve hostname my-bastion-host: nodename nor servname provided, or not known

Where "my-bastion-host" is defined as the following, in my ~/.ssh/config :

Host my-bastion-host

    HostName my-bastion.example.com

    IdentityFile ~/path/to/my/remote/keys/cert.pem

    User jpeloquin

I am using the bundled version of ssh, in /usr/bin.

If it helps any, there also seems to be an issue where sshuttle does not look for an SSH key unless specifically defined.

I have no issues using references in my ~/.ssh/config in Terminal nor in other SSH tools like "Shuttle" (the menu bar widget).

Thank you,

Jamie

[Brian May]

Jamie Peloquin <jpeloquin...@gmail.com> writes:

> For example:
>
> sudo sshuttle -Hv --remote my-bastion-host 10.1.1.1/32

sshuttle doesn't read your ~/.ssh/config file - ssh does that.

Here you are running sshuttle through sudo, so it will run ssh as root
and look for root's ~/.ssh/config file.

You sould be able to let sshuttle run sudo itself, and it should work.

(one exception: If you are using TPROXY method you do need to run it
with sudo as above; but that doesn't appear to be the case here.)
--
Brian May <br...@microcomaustralia.com.au>