Using SSH agent on mac OS

[343max]

Hey!

I can't figure out how to use the built-in ssh agent on mac OS. For obvious reasons I don't want to enter my ssh password into a clear text file, nor do I want to enter the passphrase for my ssh key into a clear text file. Do you know how I can convince your tool to use the standard mac OS ssh agent so the password stored in the keychain will be used?

[liximomo]

The REAMDE is clear. You can get the socket by runing echo $SSH_AUTH_SOCK.

[pevnak]

Hi,

first of all, thanks for the plugin. I would like to ask, if it is possible to load configuration from ssh-config and load the private key from there. I am using Mac OS, but when I have put the name of the server as in ssh-config, it was not located. Also, the passwordless login does not work either.

Thanks for help.

[nivintw]

Just as a reminder, I am also having this issue on Mac OS. I have the same problem as the original poster.
The below config works if I set my key file passphrase, but for the same reasons as the original poster I would rather not do that.
My config (with some things clearly changed):

{
    "host": "fake.server.com",
    "port": 22,
    "username": "myuser",
    "password": null,
    "protocol": "sftp",
    "agent": "/private/tmp/com.apple.launchd.OsTzEjBVX8/Listeners", #output of echo $SSH_AUTH_SOCK
    "privateKeyPath": "/valid/path/to/file",
    "passphrase": null,
    "passive": false,
    "interactiveAuth": false,
    "remotePath": "/valid/remote/path",
    "uploadOnSave": true,
    "syncMode": "update",
    "watcher": {
        "files": false,
        "autoUpload": false,
        "autoDelete": false
    },
    "ignore": [
        "**/.vscode/**",
        "**/.git/**",
        "**/.DS_Store"
    ]
}

[liximomo]

@twn346 In next release it's will prompt you to enter a passphrase. This will prevent from using cleartext passphrase in this config. Just wait a couple of days.

[dboune]

@liximomo It would be really nice if the agent socket path could be detected, or some method of saying "just use $SSH_AUTH_SOCK please". It is a, albeit minor, annoyance to have to modify that config for each project each time the socket is regenerated, typically on reboot.

[benwick]

It is a, albeit minor, annoyance to have to modify that config for each project each time the socket is regenerated, typically on reboot.

Minor annoyance? I think, this is a big problem. Please add a option to auto extract $SSH_AUTH_SOCK from the environment.

[skyrpex]

Something like "agent": true would be nice.

[liximomo]

@benwick @dboune @skyrpex In v1.2.6, you can set Environment Variable as value.

"agent": "$SSH_AUTH_SOCK"

[Charly-HID]

Generate your ssh key specifying the ecdsa algorithm type: ssh-keygen -t ecdsa (Linux) PuTTY (Windows)

{
"name": "your_remote_server_name",
"host": "123.456.789.100",
"protocol": "sftp",
"port": 1234,
"username": "remote_user_name",
"privateKeyPath": "/home/local_user_name/.ssh/id_ecdsa",
"passphrase":true,
"remotePath": "/home/remote_user_name/folderxyz",
"uploadOnSave": true,
"useTempFile": false,
"openSsh": false
}

If you don't use a passphrase when generating your ssh key, remove ("passphrase":true,) from this code.