CentOS - Aug 2010 - /bin/su wont work inside a chroot?

On centos 4 (i386 chroot on an x86_64) it just prompts me for a password.

Any suggesstion on where to start looking?

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- Jason Pyeron                      PD Inc. http://www.pdinc.us -
- Principal Consultant              10 West 24th Street #100    -
- +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
-                                                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.

> -----Original Message-----
> From: centos-bounces at centos.org 
> [mailto:centos-bounces at centos.org] On Behalf Of Jason Pyeron
> Sent: Sunday, August 01, 2010 10:34
> To: 'CentOS mailing list'
> Subject: [CentOS] /bin/su wont work inside a chroot?
> 
> On centos 4 (i386 chroot on an x86_64) it just prompts me for 
> a password.
> 
> Any suggesstion on where to start looking?
So my hack will not work either...

[root at devserver21 ~]# echo 0 >/selinux/enforce
[root at devserver21 ~]# chroot /var/mnt/192.168.1.52
[root at devserver21 /]# passwd apache
passwd: user_u:system_r:initrc_t is not authorized to change the password of
apache
[root at devserver21 /]#



--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- Jason Pyeron                      PD Inc. http://www.pdinc.us -
- Principal Consultant              10 West 24th Street #100    -
- +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
-                                                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.

Jason Pyeron <jpyeron at ...> writes:
> 
> On centos 4 (i386 chroot on an x86_64) it just prompts me for a password.
> 
> Any suggesstion on where to start looking?
> 
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> -                                                               -
> - Jason Pyeron                      PD Inc. http://www.pdinc.us -
> - Principal Consultant              10 West 24th Street #100    -
> - +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
> -                                                               -
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> This message is copyright PD Inc, subject to license 20080407P00.
> 
Just as a guess, you need to have an appropriate sudoers file in the correct
location relative to the chrooted root.  Pulling some information from one of
your follow up posts, that would be:

/var/mnt/192.168.1.52/etc/sudoers

Once you chroot, programs look for files in their normal locations but relative
to whatever the new root is.

Cheers,
Dave