search

liximomo / vscode-sftp

Super fast sftp/ftp extension for VS Code
MIT License
1.51k stars 265 forks source link

Extension host terminates in Latest version of vscode - January 2021 (version 1.53) #883

Open akkyjumbade opened 3 years ago

akkyjumbade commented 3 years ago

System Edition Windows 10 Pro Version 20H2 Installed on ‎31-‎10-‎2020 OS build 19042.789 Experience Windows Feature Experience Pack 120.2212.2020.0

codingkoala commented 3 years ago

same here running Ubuntu

lukasschreiber commented 3 years ago

same here Windows 10 Home

The Extension Host terminates with any sftp Extensions for VS Code since the update

terrycgao commented 3 years ago

Same here. Windows 10 Home

tukerty commented 3 years ago

same MacOs - Big Sur VsCode - 1.53.0 liximomo.sftp - 1.12.9

tamasgt commented 3 years ago

Same here. Windows 10 Pro VsCode: 1.53.0 SFTP: 1.12.9

the88g commented 3 years ago

+1 I've rolled back to November and disabled auto updates for the first time :(

chenyekun1 commented 3 years ago

Same bug here. Windwos 10 LTSC 1809 VS Code : 1.53.0 SFTP : 1.12.9 I think maybe this extension not compatible with the latest version of VS Code?

ZxGame00 commented 3 years ago

Same bug here. macOs Catalina 10.15.7 Vs Code：1.53.0 SFTP：1.12.9

oktayaydogan commented 3 years ago

same MacOs - Big Sur VsCode - 1.53.0 liximomo.sftp - 1.12.9

averywu commented 3 years ago

Same MacOSX - 10.15.7 VSCode - 1.53.0 liximomo.sftp - 1.12.9

Console : workbench.desktop.main.js:60 [IPC Library: File Watcher (nsfw)] (node:3988) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 uncaughtException listeners added to [process]. Use emitter.setMaxListeners() to increase limit b @ workbench.desktop.main.js:60 workbench.desktop.main.js:60 [Extension Host] (node:3987) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. b @ workbench.desktop.main.js:60 workbench.desktop.main.js:1734 Extension host terminated unexpectedly. Code: null Signal: SIGSEGV _onExtensionHostCrashed @ workbench.desktop.main.js:1734 workbench.desktop.main.js:618 ERR Extension host terminated unexpectedly. The following extensions were running: vscode.microsoft-authentication, vscode.debug-auto-launch, vscode.emmet, vscode.merge-conflict, vscode.testing-editor-contributions, ms-vscode.js-debug, vscode.github-authentication, vscode.configuration-editing, vscode.extension-editing, vscode.json-language-features, vscode.npm, liximomo.sftp workbench.desktop.main.js:738 Extension host terminated unexpectedly. onDidChangeNotification @ workbench.desktop.main.js:738 DevTools failed to load SourceMap: Could not load content for https://ticino.blob.core.windows.net/sourcemaps/8490d3dde47c57ba65ec40dd192d014fd2113496/core/bootstrap.js.map: DevTools failed to load SourceMap: Could not load content for https://ticino.blob.core.windows.net/sourcemaps/8490d3dde47c57ba65ec40dd192d014fd2113496/core/vs/workbench/workbench.desktop.main.js.map: Load canceled due to load timeout

ghost commented 3 years ago

Same here MacOSX - 10.15.7 VSCode - 1.53.0 liximomo.sftp - 1.12.9

allexandry commented 3 years ago

Same here. Windows 10 Pro VsCode: 1.53.0 SFTP: 1.12.9

Important !

sevenleo commented 3 years ago

Temporary solution: Rollback Vscode to version 1.52 and disable updates https://code.visualstudio.com/updates/v1_52

https://stackoverflow.com/questions/49346733/how-to-downgrade-vscode

ddirks commented 3 years ago

Same here. Windows 10 Pro VsCode: 1.53.0 SFTP: 1.12.9

I am connecting to a centos server (Linux 2.6.32-754.30.2.el6.x86_64) tunneled via a gateway machine running Solaris (5.10 Generic_153153-01 sun4v sparc) if that's useful information.

Rolling back to VScode version 1.52 does provide a workaround.

insuns commented 3 years ago

same MacOs - Big Sur VsCode - 1.53.0 liximomo.sftp - 1.12.9

ericzhao007 commented 3 years ago

+1

jiankafei commented 3 years ago

+1

ericzhao007 commented 3 years ago

只有使用私钥的时候才有这个问题，使用账号密码是正常的

jiankafei commented 3 years ago

使用账号密码也有这个问题，win10

zorapeteri commented 3 years ago

Same here

MacOS Big Sur v11.1 VSCode v1.53.0 liximono.sftp v1.12.9

Hopfrosch commented 3 years ago

Same problem here! Windwos 10 VS Code : 1.53.0 SFTP : 1.12.9

I went back to version 1.51 from October and it worked. Version 1.52 did not work for me.

ylihao commented 3 years ago

Yup same here.

MacOS BigSur 11.2 VSC 1.53.0 SFTP 1.12.9

pacoVela commented 3 years ago

Same: Debian 10.8 rolled back to 1.52 solves it... :(

elvenfighter commented 3 years ago

Confirming on Ubuntu 20.10 x86_64. Attaching develper console logs -1612869483251.log

allexandry commented 3 years ago

It work for me thanks.

Koffivi Sehyram DJOKOUI PDG WCC-WALLET S.A.

Le lun. 8 févr. 2021 à 23:53, Leonardo Neves notifications@github.com a écrit :

Temporarily solve: Rollback Vscode to version 1.52 and disable updates https://code.visualstudio.com/updates/v1_52

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/liximomo/vscode-sftp/issues/883#issuecomment-775517559, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADX56MQUSILCNFHB5CFXE4LS6BTQNANCNFSM4XGDXHSQ .

6b796b75 commented 3 years ago

broken by https://github.com/electron/electron/issues/27673 temp solution is to not use diffie-hellman key exchange method comment out/update KexAlgorithms in server sshd config (/etc/ssh/sshd_config)

isildrum commented 3 years ago

Same here. Windows 10 Pro VS Code 1.53 SFTP 1.12.9

KFRANCMM commented 3 years ago

I tried the December version, but it didn't work

Version: 1.52.1 (system setup)
Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523
Date: 2020-12-16T16:34:46.910Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.18363

Debug output

[02-09 12:23:52] [debug] Client: Trying 10.20.5.5 on port 5600 ...
[02-09 12:23:52] [debug] Client: Connected
[02-09 12:23:52] [debug] Remote ident: 'SSH-2.0-OpenSSH_5.5'
[02-09 12:23:52] [debug] Outgoing: Writing KEXINIT
[02-09 12:23:52] [debug] DEBUG: Comparing KEXINITs ...
[02-09 12:23:52] [debug] (local) KEX algorithms: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
[02-09 12:23:52] [debug] (remote) KEX algorithms: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
[02-09 12:23:52] [debug] KEX algorithm: diffie-hellman-group-exchange-sha256
[02-09 12:23:52] [debug] (local) Host key formats: ssh-ed25519,ssh-rsa,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
[02-09 12:23:52] [debug] (remote) Host key formats: ssh-rsa,ssh-dss
[02-09 12:23:52] [debug] Host key format: ssh-rsa
[02-09 12:23:52] [debug] (local) Client->Server ciphers: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm,aes128-gcm@openssh.com,aes256-gcm,aes256-gcm@openssh.com
[02-09 12:23:52] [debug] (remote) Client->Server ciphers: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
[02-09 12:23:52] [debug] Client->Server Cipher: aes128-ctr
[02-09 12:23:52] [debug] (local) Server->Client ciphers: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm,aes128-gcm@openssh.com,aes256-gcm,aes256-gcm@openssh.com
[02-09 12:23:52] [debug] (remote) Server->Client ciphers: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
[02-09 12:23:52] [debug] Server->Client Cipher: aes128-ctr
[02-09 12:23:52] [debug] (local) Client->Server HMAC algorithms: hmac-sha2-256,hmac-sha2-512,hmac-sha1
[02-09 12:23:52] [debug] (remote) Client->Server HMAC algorithms: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
[02-09 12:23:52] [debug] Client->Server HMAC algorithm: hmac-sha1
[02-09 12:23:52] [debug] (local) Server->Client HMAC algorithms: hmac-sha2-256,hmac-sha2-512,hmac-sha1
[02-09 12:23:52] [debug] (remote) Server->Client HMAC algorithms: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
[02-09 12:23:52] [debug] Server->Client HMAC algorithm: hmac-sha1
[02-09 12:23:52] [debug] (local) Client->Server compression algorithms: none,zlib@openssh.com,zlib
[02-09 12:23:52] [debug] (remote) Client->Server compression algorithms: none,zlib@openssh.com
[02-09 12:23:52] [debug] Client->Server compression algorithm: none
[02-09 12:23:52] [debug] (local) Server->Client compression algorithms: none,zlib@openssh.com,zlib
[02-09 12:23:52] [debug] (remote) Server->Client compression algorithms: none,zlib@openssh.com
[02-09 12:23:52] [debug] Server->Client compression algorithm: none
[02-09 12:23:52] [debug] Outgoing: Writing KEXDH_GEX_REQUEST
[02-09 12:24:07] [debug] Outgoing: Writing KEXDH_GEX_INIT
[02-09 12:24:09] [debug] Outgoing: Writing DISCONNECT (BY_APPLICATION)
vikicoder007 commented 3 years ago

Same here. Windows 10 Pro VS Code 1.53.1 SFTP 1.12.9

R4xx4r commented 3 years ago

Same here

OS: Ubuntu 20.10

VS Code:

Version: 1.53.0
Commit: 8490d3dde47c57ba65ec40dd192d014fd2113496
Date: 2021-02-03T15:56:04.185Z
Electron: 11.2.1
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Linux x64 5.8.0-43-generic

SFTP: 1.12.9

babache commented 3 years ago

Downgrade temporary VSC for continue to use..

mr-scrpt commented 3 years ago

Same here. WIN 10

tmaegawa-jci commented 3 years ago

Same problem from Feb. 9 Windows 10 Pro VS Code 1.53.1 SFTP 1.12.9

dparso commented 3 years ago

+1 Catalina 10.15.7 VSCode 1.53.2

gitccchub commented 3 years ago

Same problem Ubuntu 20.04 VS Code 1.53.2 SFTP 1.12.9 Rolled back to 1.52 solves it.

crismas06 commented 3 years ago

Same problem Windows 10 Pro VS Code 1.53.2 SFTP 1.12.9

VS Code 1.52 works.

Ben-Voris commented 3 years ago

See above. vscode-sftp appears to be a victim of this VS Code issue #116260 Any SSH File system extension will crash VS Code in a similar way - Buffer() is deprecated @ console.ts:137, which, in turn, is caused by Electron issue #27673 Electron v11 breaks crypto.createDiffieHellman with non-number generators

The key message from the console is this:

console.ts:137 [Extension Host] (node:21932) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead

So, it appears that watching this issue is useless. Electron issue #27673 is already closed. VSCode issue #116260 is the one to watch.

3b0b commented 3 years ago

The impression I got during my own testing was that the message about Buffer() being deprecated is actually coincidental and unrelated to the underlying createDiffieHellman problem, because I'm almost positive I still saw that in the console on the versions that didn't crash...but it's entirely possible I'm wrong, and it's probably also not very important whether I'm right or not.

arvislacis commented 3 years ago

For other users facing this issue - as the main problem is related to the Electron and createDiffieHellman then you can disable/remove "diffie-hellman-group-exchange-sha256" algorithm as specified in Wiki - SFTP only Config.

In other words, you need to edit sftp.json file and specify following algorithms as supported for each SFTP profile:

"algorithms": {
    "kex": [
        "ecdh-sha2-nistp256",
        "ecdh-sha2-nistp384",
        "ecdh-sha2-nistp521",
        "diffie-hellman-group14-sha1"
    ],
    "cipher": [
        "aes128-ctr",
        "aes192-ctr",
        "aes256-ctr",
        "aes128-gcm",
        "aes128-gcm@openssh.com",
        "aes256-gcm",
        "aes256-gcm@openssh.com"
    ],
    "serverHostKey": [
        "ssh-rsa",
        "ecdsa-sha2-nistp256",
        "ecdsa-sha2-nistp384",
        "ecdsa-sha2-nistp521"
    ],
    "hmac": [
        "hmac-sha2-256",
        "hmac-sha2-512",
        "hmac-sha1"
    ]
}

^ As you can see "diffie-hellman-group-exchange-sha256" is not specified. After doing this everything works fine with 1.53.x versions. Not really the best solution but still.

oberocks commented 3 years ago

+1 same issue

Also, this applies to ftp/sftp functionality as well as ssh for me. So the awesome suggestion by @arvislacis didn't work for my environment. It did remove the crash in vs code, but ultimately failed silently on the server side (which may be due to my host's setup - but figured it might help.)

edit: ps - reverting to vscode 1.52.1 defs DID fix the issue. woohoo.

yangdezuan commented 3 years ago

Same problem from Feb. 15 Windows 10 Pro VS Code 1.53.2 SFTP 1.12.9

什么时候能修复，现在只能vscode 降到1.53以下版本1.50;

jordanyep commented 3 years ago

Same here for me, tested on both Windows and Mac environments

yikeda6616 commented 3 years ago

same here on macOS Catalina 10.15.7

bansan85 commented 3 years ago

Now, it looks like there is a workaround (https://github.com/liximomo/vscode-sftp/issues/883#issuecomment-778684682). Please, report your case only if the workaround does not work. Thanks,

manuzcom commented 3 years ago

When connect to centos 7 ssh server has no error occurs. But when connect to centos 6 ssh server has same problem.

gaelganlut commented 3 years ago

Now, it looks like there is a workaround (#883 (comment)). Please, report your case only if the workaround does not work. Thanks,

Not working :( Extension stopped working since today for me Im getting these errors:

(this one when i reenable the extension)abstractExtensionService.ts:718 [liximomo.sftp]: A view with id remoteExplorer is already registered. _logMessageInConsole @ abstractExtensionService.ts:718 _handleExtensionPointMessage @ abstractExtensionService.ts:671 K @ abstractExtensionService.ts:645 _msg @ extensionsRegistry.ts:36 error @ extensionsRegistry.ts:45 (anonymous) @ viewsExtensionPoint.ts:447 (anonymous) @ viewsExtensionPoint.ts:440 A @ collections.ts:42 addViews @ viewsExtensionPoint.ts:425 (anonymous) @ viewsExtensionPoint.ts:413 _handle @ extensionsRegistry.ts:141 acceptUsers @ extensionsRegistry.ts:132 _handleExtensionPoint @ abstractExtensionService.ts:705 _doHandleExtensionPoints @ abstractExtensionService.ts:651 _deltaExtensions @ abstractExtensionService.ts:253 async function (async) _deltaExtensions @ abstractExtensionService.ts:210 _handleDeltaExtensions @ abstractExtensionService.ts:194 (anonymous) @ abstractExtensionService.ts:152 fire @ event.ts:623 setEnablement @ extensionEnablementService.ts:152 async function (async) setEnablement @ extensionEnablementService.ts:149 doSetEnablement @ extensionsWorkbenchService.ts:1177 checkAndSetEnablement @ extensionsWorkbenchService.ts:1104 promptAndSetEnablement @ extensionsWorkbenchService.ts:1067 setEnablement @ extensionsWorkbenchService.ts:931 run @ extensionsActions.ts:1129 runAction @ actions.ts:203 run @ actions.ts:195 onClick @ actionViewItems.ts:163 (anonymous) @ menu.ts:454 setTimeout (async) (anonymous) @ menu.ts:453 console.ts:137 [Extension Host] (node:19744) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. b @ console.ts:137 $logExtensionHostMessage @ mainThreadConsole.ts:35 _doInvokeHandler @ rpcProtocol.ts:409 _invokeHandler @ rpcProtocol.ts:394 _receiveRequest @ rpcProtocol.ts:310 _receiveOneMessage @ rpcProtocol.ts:237 (anonymous) @ rpcProtocol.ts:105 fire @ event.ts:623 fire @ ipc.net.ts:468 _receiveMessage @ ipc.net.ts:821 (anonymous) @ ipc.net.ts:660 fire @ event.ts:623 acceptChunk @ ipc.net.ts:241 (anonymous) @ ipc.net.ts:202 I @ ipc.net.ts:32 emit @ events.js:315 addChunk @ _stream_readable.js:295 readableAddChunk @ _stream_readable.js:271 Readable.push @ _stream_readable.js:212 onStreamRead @ internal/stream_base_commons.js:186 abstractExtensionService.ts:466 Extension host terminated unexpectedly. Code: 3221225477 Signal: null

aesculus commented 3 years ago

The https://github.com/liximomo/vscode-sftp/issues/883#issuecomment-778684682 fix worked for me.

nicokaiser commented 3 years ago

While #883 seems to workaround the problem for some situations, it is not a universal fix, as some servers do not support other key exchange algorithms, and changing this is beyond the influcence.

mean-cj commented 3 years ago

The #883 (comment) fix worked for me.

confirm work for now.

yangdezuan commented 3 years ago

The #883 (comment) fix worked for me.

confirm work for now. thanks!