lukasz-wronski / vscode-ftp-sync

Ftp Sync plugin for Visual Studio Code
https://marketplace.visualstudio.com/items/lukasz-wronski.ftp-sync
320 stars 85 forks source link

Nothing when try to connect my ssh server with privatekey #179

Open JAClaveroGarcia opened 7 years ago

JAClaveroGarcia commented 7 years ago

My config:

{
    "remotePath": "/home/username/DWES",
    "host": "myhost",
    "username": "username",
    "password": null,
    "port": 22,
    "secure": true,
    "protocol": "sftp",
    "uploadOnSave": false,
    "passive": false,
    "debug": false,
    "privateKeyPath": "/home/username/.ssh/id_rsa",
    "passphrase": null,
    "ignore": [
        "\\.vscode",
        "\\.git",
        "\\.DS_Store"
    ],
    "generatedFiles": {
        "uploadOnSave": false,
        "extensionsToInclude": [],
        "path": "/home/jaclaverogarcia/DWES"
    }
}

I have reviewed and there are no errors in the connection data. I make connections to my server periodically with this credential. I use the privatekey method and it has no passphrase. When I try to connect the ssh server does not even receive the connection attempt. I do not know if it is a bug in the extension or I have something wrong in the configuration. I currently have version 0.3.3 of ftp-sync and 1.12.2 of VSCode.

hobbyman commented 7 years ago

Same here. I've been working on this the last couple of days. I'm on a Mac. My config is just like yours. But I get this message: Error: All configured authentication methods failed

yoni333 commented 7 years ago

me too

Seegras commented 2 years ago

Because ssh-rsa using SHA1 is NOT acceptable crypto anywhere in this world. Needs to use ssh-rsa-sha256.

This is how this would presumably look on the server side: Unable to negotiate with IP port PORT: no matching host key type found. Their offer: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-rsa,ssh-dss [preauth]

These are all insecure.

The contemporary ones rsa-sha2-256, rsa-sha2-512 and ed25519 are missing.

Note that this is not a problem with the users keys, but with the key-exchange the extension tries to do.