[scponly] scp failing in chrooted environment

[Paul Jones]

That very well could be the problem. I am running on suse linux with 
openssh. I am using pam_ldap and nss_ldap to lookup the users and so forth. 
So, /etc/passwd does not have the user info in it. Any idea what needs to be 
in the chrooted environment for pam_ldap to work?

Paul

On Apr 11, 2005 12:55 PM, Paul Hyder <Paul.Hyder at noaa.gov> wrote:
> 
> Which operating system and ssh? (e.g. The OpenSSH scp calls getpwuid to
> verify the UID and since it is run after the chroot it could be something
> simple like your chrooted /etc/passwd is missing or unreadable; but the
> passwd file isn't always the cause. With OpenSSH it does mean the
> getpwuid is returning NULL.)
> Paul Hyder
> NOAA Forecast Systems Lab
> Boulder, CO.
> 
> Paul Jones wrote:
> > I have set up scponly and it is almost working perfectly. I use it with 
> the
> > chroot option. rsync works, sftp works, but scp does not. scp complains:
> > "unknown user 10001" 10001 is the correct user id. I am thinking that I 
> have
> > just left something out the the chrooted area that it needs, but I can 
> not
> > figure out what. usr/bin/id, usr/bin/groups, usr/bin/scp are all there. 
> Any
> > thoughts about what might be wrong?
> >
> > Paul
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > scponly mailing list
> > scponly at lists.ccs.neu.edu
> > https://lists.ccs.neu.edu/bin/listinfo/scponly
>
-------------- next part --------------
HTML attachment scrubbed and removed