This is the mail archive of the
mailing list for the Cygwin project.
Re: OpenSSH - sftp not working for non-Administrator users
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 5 Oct 2009 20:50:34 +0200
- Subject: Re: OpenSSH - sftp not working for non-Administrator users
- References: <4A6388BB.email@example.com> <4A63CD77.firstname.lastname@example.org> <20090720023742.GC15540@ednor.casa.cgf.cx> <4A63E12B.email@example.com> <20090720050320.GD15540@ednor.casa.cgf.cx> <4A6404C4.firstname.lastname@example.org> <email@example.com> <20090720115728.GD30066@calimero.vinschen.de> <firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
On Oct 5 16:07, Julio Costa wrote:
> On Mon, Jul 20, 2009 at 12:57, Corinna Vinschen wrote:
> > Nevertheless there's something fishy. ?The /bin path is added
> > automatically by cygrunsrv so that the service doesn't have to care for
> > a default $PATH by itself. ?I assume it has something to do with path
> > permissions. ?Check the ACLs.
> ... the reason is, I myselft stumped into something similar.
> After configuring openssh with chrooted sessions, I can login into one
> of these sessions (with a non-admin users), but any command that I try
> fail silently (unless it is a built-in).
> From what I observed with the help of process monitor, is that any
> failing command try to load cygwin1.dll from the current directory
> (/bin) but will fail, because the dll in in /usr/bin.
> This difference (/bin vs /usr/bin) is not of importance to the
> majority of the cases because: a) /bin and /usr/bin are mirrors of
> each other , through mount magic; b) /usr/bin is also in the PATH.
> But in a sshd chrooted environment thigs are different: there is no
> mount -magic, and the .dlls get copied to the /usr/bin, following
> "advice" from ldd. The PATH also only have /bin, which don't help.
> So, I was thinking, shouldn't make more sense that cygrunsrv do:
> a) add /usr/bin also as a bare-minimum, to cover chrooted environments
> (and to follow the /usr/bin/*.dll dependencies of cygwin binaries);
Why don't you just put cygwin1.dll into $CHROOT-DIR/bin?
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple