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 -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
