From: Bret Jordan <jordan@coe.utah.edu>
To: cygwin@cygwin.com
Subject: sftp-server
Date: Mon, 08 Jan 2001 10:48:00 -0000 [thread overview]
Message-ID: <5.0.2.1.0.20010108113218.00a582d0@imap.coe.utah.edu> (raw)
Situation:
I am still having problems getting sftp-server to work right. I am running
NT4.0 with sp6a. And I just performed (5 minutes ago) an Internet install
of the latest cygwin.dll, bash, and openssh. I have ssh.com's client
version 2.3.
Problem:
When ever I try to use /home/jordan in my passwd file sftp dies. If I try
and use / it works, but I can not see any of the files/directories. If I
then try to change directory to /home/jordan it dies. In fact if I try to
change directories to anything it dies. When using / as my home directory
I can upload files and make directories (even though I can not see them in
the sftp client window), they are there in the file system.
Passwd file:
jordan::1002:513:,S-1-5-21-2101946335-1589071585-740312968-1002:/home/jordan:/bin/sh
sshd_config:
Port 22
ListenAddress X.X.X.X
Protocol 2
HostDSAKey /etc/sshd_host_dsa_key
AllowUsers jordan
PasswordAuthentication yes
PermitEmptyPasswords no
KeepAlive no
PrintMotd no
CheckMail no
IgnoreRhosts yes
IgnoreUserKnownHosts yes
RhostsAuthentication no
RhostsRSAAuthentication no
Subsystem sftp /usr/sbin/sftp-server
MaxStartups 10:30:60
Error code from sshd d when I try to use /home/jordan in passwd file.
subsystem request for sftp
debug1: subsystem: exec() /usr/sbin/sftp-server
debug1: fd 10 setting O_NONBLOCK
debug1: fd 10 IS O_NONBLOCK
debug1: Received SIGCHLD.
debug1: session_by_pid: pid 200
debug1: session_exit_message: session 1 channel 1 pid 200
debug1: session_exit_message: release channel 1
debug1: channel 1: write failed
debug1: channel 1: output open -> closed
debug1: channel 1: close_write
debug1: channel 1: read failed
debug1: channel 1: input open -> drain
debug1: channel 1: close_read
debug1: channel 1: input: no drain shortcut
debug1: channel 1: ibuf empty
debug1: channel 1: input drain -> closed
debug1: channel 1: send eof
debug1: session_free: session 1 pid 200
debug1: channel 1: read<=0 rfd 10 len -1
debug1: channel 1: read failed
error: channel 1: internal error: we do not read, but chan_read_failed for
istat
e 8
debug1: channel 1: send close
debug1: channel 1: rcvd close
debug1: channel 1: full closed2
debug1: channel_free: channel 1: status: The following connections are open:
#0 server-session (t4 r0 i1/0 o16/0 fd 7/3)
#1 server-session (t4 r1 i8/0 o128/0 fd 10/10)
Thanks in advance,
Bret
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bret Jordan Dean's Office
LAN Manager College of Engineering
801.585.3765 University of Utah
jordan@coe.utah.edu
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2001-01-08 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 10:48 Bret Jordan [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-21 12:14 sftp-server Bret Jordan
2000-12-19 13:32 sftp-server Bret Jordan
2000-12-19 13:49 ` sftp-server Corinna Vinschen
2000-12-29 9:59 ` sftp-server Nicholas Sushkin
2000-12-29 10:37 ` sftp-server Bret Jordan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.0.2.1.0.20010108113218.00a582d0@imap.coe.utah.edu \
--to=jordan@coe.utah.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).