[scponly] failed: /usr/libexec/openssh/sftp-server with error No such file or directory(2)

[Peter Weil]

A quick update. Following some previous, similar threads, I ran 'ldd / 
bin/sh' and copied the libraries -- actually the entire /lib64  
directory -- into the chroot directory. I also copied /bin/sh over.  
The connection still fails, although the secure log no longer reports  
the failure and error I cited in my previous message. Instead, it  
simply closes the connection with no error:

Mar 11 08:02:04 ruby scponly[10714]: running: /usr/libexec/openssh/ 
sftp-server (username: kahewson(509), IP/port: 144.92.105.153 50088 22)
Mar 11 08:02:04 ruby scponly[10714]: about to exec "/usr/libexec/ 
openssh/sftp-server" (username: kahewson(509), IP/port: 144.92.105.153  
50088 22)
Mar 11 08:02:04 ruby sshd[10711]: pam_unix(sshd:session): session  
closed for user kahewson

Maybe this will ring a bell with someone? In any case, I'm still  
stumped and seeking a solution. I guess I'll run ldd on all of the  
other binaries.

-Peter

On Mar 10, 2008, at 4:08 PM, Peter Weil wrote:

> I've done about a half dozen scponly installs, but not for over a
> year. I'm getting this error when I try to connect for my test user
> (this is from the secure log):
>
> Mar 10 15:52:27 ruby scponly[29117]: failed: /usr/libexec/openssh/ 
> sftp-
> server with error No such file or directory(2) (username:
> kahewson(509), IP/port: 144.92.105.153 49501 22)

--
Peter Weil, Web Developer
University Communications
University of Wisconsin-Madison
Phone: 608-262-6538
Email: plweil at wisc.edu