Bug 159256

Summary: SFTP subsystem doesn't work.
Product: Red Hat Enterprise Linux 4 Reporter: Ali-Reza Anghaie <ali>
Component: opensshAssignee: Tomas Mraz <tmraz>
Status: CLOSED NOTABUG QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: shillman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-06-26 02:02:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ali-Reza Anghaie 2005-05-31 21:40:24 UTC 
Description of problem:

SFTP subsystem doesn't work. Fails silently while SCP works fine.

Version-Release number of selected component (if applicable):

openssh-3.9p1-8.RHEL4.1

How reproducible:

Always.

Steps to Reproduce:
1. Just try inbound SFTP on a stock RHEL 4 machine.
2.
3.
  
Actual results:

SFTP inbound fails.

Expected results:

SFTP inbound should work.

Additional info:

All it does is create nice secure log entries like:

May ## ##:##:## hostname sshd[11537]: subsystem request for sftp

And nothing else. The client fails to connect regardless of client. SCP works
fine. No process I can see via ps or top seems to actually be launched on the
server side. Haven't tried tracing or debug mode yet, will update with debug
after I get these mass migrations done via SCP first.
Comment 4 Tomas Mraz 2005-06-06 13:28:25 UTC 
I couldn't reproduce this problem here do you have more information? F. E. exact
commands which fail, architecture of the HW, the debugging logs and so on.
Comment 5 Ali-Reza Anghaie 2005-06-26 02:02:48 UTC 
The problem seems to be unique to when I'm using a WinSCP client. The logging
shows nothing useful, it just drops. Verbose doesn't help either.... just
*poof*. I haven't captured a session via Ethereal but I'm unsure that's going to
be fruitful. Since it's unique to the WinSCP client (tried various versions
too), I'm closing this bug.