VitalyKondratiev/vscode-sshextension

Password is not auto entered

Opened this issue · 14 comments

l2dev commented

I defined password in my serverlist configuration.

After I connect to my SSH server the password is not auto entered. I have to enter it manually.

After I exit from my SSH session then I see my password being auto entered which crashes the extension:

mypassword: The term 'mypassword' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if
a path was included, verify that the path is correct and try again.
At line:1 char:1
+ mypassword
+ ~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (mypassword:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

So my guess is that the SSH session stops the auto password entering command, and it gets executed only after SSH session is closed.

Please give me information about your OS. And after that, I will try to debug the extension under this OS to reproduce the error.

I have the same issue, My OS is windows 10 and my remote server has a linux raspbian (Raspberry Pi).

I have the same issue, My OS is windows 10 and my remote server has a linux raspbian (Raspberry Pi).

Hello, give me your config (without a password and host). I also use Windows 10 + ssh on RPi.

My config works fine:

    "sshextension.serverList": [
        {
            "name": "vk",
            "host": "****kondratiev.ru",
            "port": 22,
            "username": "pi",
            "password": "********",
            "path": "/",
            "customCommands": [
              "pwd"
            ]
        },
    ],

I have the same issue. The password is not being submitted. Also, 'path' is supposed to navigate to that directory correct? It doesn't seem to being doing that. And I can't get custom commands to run as well. I'm on Windows 10. Here is my config.

"sshextension.serverList": [
    {
        "name": "Local Server",
        "host": "192.168.1.108",
        "port": 22,
        "username": "kyle",
        "password": "*********",
        "path": "/home/kyle/myfolder",
        "customCommands": [
            "ls"
          ]
    }
]

same issue here

same issue here, with Windows 10 64 bits.

Same happens here, I'm on OSX 10.14.2

Same here. Windows 10 x64

I have the same problem. Connects to the server, but asks for a password, then goes to the root directory, instead of the one I specified.

settings.js

"sshextension.serverList": [
	{
		"name": "my-name",
		"host": "my-host",
		"port": 22,
		"username": "my-username",
		"password": "me-password", // Does not work
		"path": "need-path" // Does not work
	},
],

Same Problem. NEITHER of my Agent, Key Files OR Passwords are taken by any of the Configs (SSExtension config, Simple-sftp config) for ANY of my Hosts WHILE other extensions like SSH FS are just working fine with exactly the same settings and hosts.
Linked to this one, because they are closely related: #10 (comment)

I seriously have no idea on what I am doing wrong. it has to be a bug in the extension itself because I basically tried EVERYTHING else by now.
https://media.giphy.com/media/pPhyAv5t9V8djyRFJH/giphy.gif

@VitalyKondratiev THIS DEFINITELY DOESNT WORK AT ALL: #10 (comment)

7 months, any word? Like everyone else, my password is not being automatically entered.

I have the same issue, My OS is windows 10 and my remote server has a linux raspbian (Raspberry Pi).

Hello, give me your config (without a password and host). I also use Windows 10 + ssh on RPi.

My config works fine:

    "sshextension.serverList": [
        {
            "name": "vk",
            "host": "****kondratiev.ru",
            "port": 22,
            "username": "pi",
            "password": "********",
            "path": "/",
            "customCommands": [
              "pwd"
            ]
        },
    ],

Facing issue,
OS: Mac 10.14.5
In my case my login command and password print before terminal boot properly.

Suggestion: Add some latency, after open terminal add password filling, 2seconds might be okay on configuration manageable

Hello, I have same issue

MacOS 13.1