Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] chroot over ssh with pam_chroot

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: "Mathieu L." <lejatorn AT smgl.homelinux.net>
  • To: Mads Laursen <smgl AT dossen.dk>
  • Cc: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] chroot over ssh with pam_chroot
  • Date: Mon, 20 Dec 2004 02:32:22 +0100

On Mon, Dec 20, 2004 at 12:51:18AM +0100, Mads Laursen wrote:

> It's been awfully long since I did any serious chrooting, but I seem
> to recall that the "I have no name!" issue is related to the libraries
> available in the current view of the filesystem.
>
> Could you try to chroot and run 'find /'? What's in /lib and /usr?
>
> Try to unpack the compile-cache files for a really barebones system
> (glibc, bash, that sort of thing) into the chroot. Does that fix it?
>
> Try to run 'ldd `type -p passwd`' and anything else relevant in the
> chroot. On my box it gives:
> linux-gate.so.1 => (0xffffe000)
> libcrypt.so.1 => /lib/libcrypt.so.1 (0x40029000)
> libc.so.6 => /lib/libc.so.6 (0x40055000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> so those libs need to be in the chroot to run passwd (unless you build
> a static passwd into the chroot (might not be a bad idea if it is only
> for very specific purposes)).
>
> Hope this helps.
>
> /dossen

Of course I had ldded every bins I put in the chroot to know which libs
I should copy, and subsequently copied those.
I'm not even at the point where I have to worry about passwd itself
since the user is not yet recognized.
The unpacking solution seems odd, in all the docs I've read it was enough
to cp a few bins like the shell plus what ldd returned for this bins, and
/etc/passwd, group and shadow files. However I'll try that later and let
you know how it turned out.
Thx for the reply,

Mathieu.




Archive powered by MHonArc 2.6.24.

Top of Page