starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Cannnot use sftp #6847

New Issue
Closed
opened 2026-01-31 00:48:47 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 00:48:47 +00:00
Owner
Copy Link

Originally created by @StinGer-ShoGuN on GitHub (Mar 12, 2020).

Hi folks !

I've came across an unexpected issue when trying to download some stuff with sftp using Windows Terminal.

Environment

Windows build number: 18362.239 (Windows 10 1903)
Windows Terminal version (if applicable): 0.9.433.0

openSSH (delivered with Windows 10): OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5

Steps to reproduce

In my .ssh directory, I have a config with hosts definitions and settings. I have not tried wiping this one out to see if this changes anything.

sftp host_in_config

Expected behavior

Ability to type in commands in the sftp prompt.

Actual behavior

It is impossible to enter any command, anything or whatsoever. I can't even quit sftp. The prompt keeps awaiting for inputs that... I cannot give.
I had to kill the sftp process.

I tried it in a conhost PowerShell window, and I could use it as expected.

Good hunt ! 😉

EDIT
Fixed Windows Terminal version.

Originally created by @StinGer-ShoGuN on GitHub (Mar 12, 2020). Hi folks ! I've came across an unexpected issue when trying to download some stuff with `sftp` using Windows Terminal. # Environment ```none Windows build number: 18362.239 (Windows 10 1903) Windows Terminal version (if applicable): 0.9.433.0 openSSH (delivered with Windows 10): OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5 ``` # Steps to reproduce In my `.ssh` directory, I have a `config` with hosts definitions and settings. I have not tried wiping this one out to see if this changes anything. ```powershell sftp host_in_config ``` # Expected behavior Ability to type in commands in the `sftp` prompt. # Actual behavior It is impossible to enter any command, anything or whatsoever. I can't even quit `sftp`. The prompt keeps awaiting for inputs that... I cannot give. I had to kill the `sftp` process. I tried it in a conhost PowerShell window, and I could use it as expected. Good hunt ! 😉 **EDIT** Fixed Windows Terminal version.
claunia commented 2026-01-31 00:48:48 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Mar 12, 2020):

openSSH (delivered with Windows 10): OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5

Did you try updating your OpenSSH to 8.1 and check again? Some changes were made that may make working in Terminal better. I do not have problems using Terminal with the latest but I haven't attempted to use sftp either. I use scp instead and that has always worked.

@WSLUser commented on GitHub (Mar 12, 2020): >openSSH (delivered with Windows 10): OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5 Did you try updating your OpenSSH to 8.1 and check again? Some changes were made that may make working in Terminal better. I do not have problems using Terminal with the latest but I haven't attempted to use sftp either. I use scp instead and that has always worked.
claunia commented 2026-01-31 00:48:48 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 13, 2020):

I can't actually reproduce this on my machine with sftp from 7.7p1. Can you share a bit more information about your system? What sort of keyboard layout are you using?

@DHowett-MSFT commented on GitHub (Mar 13, 2020): I can't actually reproduce this on my machine with sftp from 7.7p1. Can you share a bit more information about your system? What sort of keyboard layout are you using?
claunia commented 2026-01-31 00:48:48 +00:00
Author
Owner
Copy Link

@StinGer-ShoGuN commented on GitHub (Mar 16, 2020):

openSSH (delivered with Windows 10): OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5

Did you try updating your OpenSSH to 8.1 and check again? Some changes were made that may make working in Terminal better. I do not have problems using Terminal with the latest but I haven't attempted to use sftp either. I use scp instead and that has always worked.

I'm not talking about OpenSSH in a Linux subsystem here, I'm talking about the one embedded in Windows 10. So no, I can't update to 8.1 (or 8.2 to be more up to date).

I can't actually reproduce this on my machine with sftp from 7.7p1. Can you share a bit more information about your system? What sort of keyboard layout are you using?

I'm using Windows in French with a QWERTY keyboard configured for entering French in a US international layout.
I did not try to switch to English input with US international. Will do.

@StinGer-ShoGuN commented on GitHub (Mar 16, 2020): > > > > openSSH (delivered with Windows 10): OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5 > > Did you try updating your OpenSSH to 8.1 and check again? Some changes were made that may make working in Terminal better. I do not have problems using Terminal with the latest but I haven't attempted to use sftp either. I use scp instead and that has always worked. I'm not talking about OpenSSH in a Linux subsystem here, I'm talking about the one embedded in Windows 10. So no, I can't update to 8.1 (or 8.2 to be more up to date). > > > I can't actually reproduce this on my machine with sftp from 7.7p1. Can you share a bit more information about your system? What sort of keyboard layout are you using? I'm using Windows in French with a QWERTY keyboard configured for entering French in a US international layout. I did not try to switch to English input with US international. Will do.
claunia commented 2026-01-31 00:48:48 +00:00
Author
Owner
Copy Link

@StinGer-ShoGuN commented on GitHub (Mar 16, 2020):

And... problem is gone. I can't reproduce it neither (I have restarted my computed since Friday, that may have helped).

@StinGer-ShoGuN commented on GitHub (Mar 16, 2020): And... problem is gone. I can't reproduce it neither (I have restarted my computed since Friday, that may have helped).
claunia commented 2026-01-31 00:48:49 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 16, 2020):

Sorry to hear that the repro went away 😦
Please let us know if it comes back.

@DHowett-MSFT commented on GitHub (Mar 16, 2020): Sorry to hear that the repro went away 😦 Please let us know if it comes back.
claunia commented 2026-01-31 00:48:49 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Mar 16, 2020):

@StinGer-ShoGuN Despite my username, I do use Windows OpenSSH as well in addition to WSL ssh. I've opened up PS many times in Terminal just to ssh to a Linux server. You can run both, just configure the WSL ssh to port 2222 or something else. And the Win32-OpenSSH release is currently pointing at 8.1. I would still suggest upgrading your OpenSSH but this sounds like you had a resource issue that was fixed by rebooting. That is probably OS specific, not Terminal or SSH (though if there's buggy code in the Win implementation of OpenSSH causing resource exhaustion, it would be worth filing an issue over there: https://github.com/PowerShell/Win32-OpenSSH)

@WSLUser commented on GitHub (Mar 16, 2020): @StinGer-ShoGuN Despite my username, I do use Windows OpenSSH as well in addition to WSL ssh. I've opened up PS many times in Terminal just to ssh to a Linux server. You can run both, just configure the WSL ssh to port 2222 or something else. And the Win32-OpenSSH release is currently pointing at 8.1. I would still suggest upgrading your OpenSSH but this sounds like you had a resource issue that was fixed by rebooting. That is probably OS specific, not Terminal or SSH (though if there's buggy code in the Win implementation of OpenSSH causing resource exhaustion, it would be worth filing an issue over there: https://github.com/PowerShell/Win32-OpenSSH)
claunia commented 2026-01-31 00:48:49 +00:00
Author
Owner
Copy Link

@StinGer-ShoGuN commented on GitHub (Mar 18, 2020):

@StinGer-ShoGuN Despite my username, I do use Windows OpenSSH as well in addition to WSL ssh. I've opened up PS many times in Terminal just to ssh to a Linux server. You can run both, just configure the WSL ssh to port 2222 or something else. And the Win32-OpenSSH release is currently pointing at 8.1. I would still suggest upgrading your OpenSSH but this sounds like you had a resource issue that was fixed by rebooting. That is probably OS specific, not Terminal or SSH (though if there's buggy code in the Win implementation of OpenSSH causing resource exhaustion, it would be worth filing an issue over there: https://github.com/PowerShell/Win32-OpenSSH)

Thanks @WSLUser, wasn't aware of the up to date releases. 👍

@StinGer-ShoGuN commented on GitHub (Mar 18, 2020): > > > @StinGer-ShoGuN Despite my username, I do use Windows OpenSSH as well in addition to WSL ssh. I've opened up PS many times in Terminal just to ssh to a Linux server. You can run both, just configure the WSL ssh to port 2222 or something else. And the Win32-OpenSSH release is currently pointing at 8.1. I would still suggest upgrading your OpenSSH but this sounds like you had a resource issue that was fixed by rebooting. That is probably OS specific, not Terminal or SSH (though if there's buggy code in the Win implementation of OpenSSH causing resource exhaustion, it would be worth filing an issue over there: https://github.com/PowerShell/Win32-OpenSSH) Thanks @WSLUser, wasn't aware of the up to date releases. 👍
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Input Issue-Bug Needs-Attention Needs-Tag-Fix Product-Terminal Resolution-No-Repro
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6847
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?