Wow, it took me five minutes to find this thread!!

DON'T CHANGE THE PERMS UNLESS YOU ARE SURE THAT THEY ARE THE freeVSD
PATCHED BINARIES.

Have you got +suid versions of these binaries in the /bin directory?

The locations of various binaries changed from 6.x to 7.x and we are
still finding out which ones. If you `rpm -qpl` the various
/usr/local/src/freevsd/pkgs/*.rpm files, this will tell you where the
freeVSD patched versions have gone. You may find that you'll need to
modify the freevsd.conf file to make sure that the un-patched versions
are removed from the various dirs, so that the patched one take
presedence.

Hope this helps,
Damion.


[EMAIL PROTECTED] wrote:
> 
> Damion,
> 
> again an older task ;)
> 
> As I looked at my /bin I found just these files with suid:
> 
> -rwsr-xr-x   11 root     root        55356 Aug  5  2000 mount
> -rwsr-xr-x   11 root     root        21680 Jan 29  2001 su
> -rwsr-xr-x   11 root     root        25404 Aug  5  2000 umount
> 
> the other suid files you had in your /bin (see you email below) are not
> there at all. Some are in /usr/bin with suid:
> 
> -rwsr-xr-x    4 root     root        19696 Jan 29  2001 chgrp
> -rwsr-xr-x    4 root     root        21412 Jan 29  2001 chmod
> -rwsr-xr-x    4 root     root        19412 Jan 29  2001 chown
> -rwsr-xr-x    4 root     root        48412 Jan 29  2001 mv
> 
> and the other files are in /usr/bin but not(!) with suid:
> 
> -rwxr-xr-x    4 root     root        28444 Jan 29  2001 rm
> -rwxr-xr-x    4 root     root        14756 Jan 29  2001 rmdir
> -rwxr-xr-x    4 root     root        50140 Jan 29  2001 ls
> -rwxr-xr-x    4 root     root        40508 Jan 29  2001 cp
> -rwxr-xr-x    4 root     root        21728 Jan 29  2001 mkdir
> 
> so, as I said, I use vsd 1.4.6 (from source) and rh7.0. No Problems o
> installation.
> 
> Why are my file locations different? Because of the source install? Can
> I just change these perms on the skel? Everything else seems to be fine.
> 
> regards
> 
> jimmy
> 
> am [Thu, 21 Jun 2001 16:50:49 +0100] schrieb Damion Parry <[EMAIL PROTECTED]> 
>:
> 
> > Excellent,
> >
> > I've just looked in my current skel and I have:
> >
> > /bin:
> > [root@vsone /bin]# ls -l | grep rws
> > -rwsr-xr-x    2 root     root        18488 Jul 18  2000 chgrp
> > -rwsr-xr-x    2 root     root        19948 Jul 18  2000 chmod
> > -rwsr-xr-x    2 root     root        18220 Jul 18  2000 chown
> > -rwsr-xr-x    2 root     root        40844 Jul 18  2000 cp
> > -rwsr-xr-x    2 root     root        49560 Jul 18  2000 ls
> > -rwsr-xr-x    2 root     root        20452 Jul 18  2000 mkdir
> > -rwsr-xr-x    2 root     root        56208 Feb  3  2000 mount
> > -rwsr-xr-x    2 root     root        48924 Jul 18  2000 mv
> > -rwsr-xr-x    2 root     root        26912 Jul 18  2000 rm
> > -rwsr-xr-x    2 root     root        12996 Jul 18  2000 rmdir
> > -rwsr-xr-x    2 root     root        19144 May 26  2000 su
> > -rwsr-xr-x    2 root     root        26608 Feb  3  2000 umount
> > [root@vsone /bin]#
> >
> > Damion.
> >
> > [EMAIL PROTECTED] wrote:
> > >
> > > Damion,
> > >
> > > yes - that was it!
> > >
> > > I did vsd-genskel.pl without any error.
> > > What /bin files has to be u+s? I guess chmod chgrp also??
> > >
> > > regards
> > >
> > > jimmy
> > >
> > > am [Thu, 21 Jun 2001 16:10:28 +0100] schrieb Damion Parry 
><[EMAIL PROTECTED]> :
> > >
> > > > Hello,
> > > >
> > > > The only thing I could think of was that the freevsd specific third part
> > > > packages had not been installed into the skel, but thats a lame excess,
> > > > and as the version of chown in you're skel is that same as that on a
> > > > rh6.2 box, I'd say that probably wasn't a cause.
> > > >
> > > > Ahh. Just spotted it. chown needs the setuid bit set, and it drops the
> > > > root perms if the user is anything but admin. How did you create this
> > > > skel?
> > > >
> > > > [root@vsone /bin]# ls -l chown
> > > > -rwsr-xr-x    2 root     root        18220 Jul 18  2000 chown
> > > > [root@vsone /bin]#
> > > >
> > > > Damion.
> > > >
> > > > [EMAIL PROTECTED] wrote:
> > > > >
> > > > > Damion,
> > > > >
> > > > > hmm - older thread, but I have the same problem now.
> > > > >
> > > > > The admin seems to have no rights to change ownership of user files.
> > > > > Your test below is not replicable - I also get the problem of stenny.
> > > > >
> > > > > vsd 1.4.6 (from source)
> > > > > rh7.0
> > > > >
> > > > > no problems on installation
> > > > >
> > > > > [admin@linux11 bin]$ ll | grep chown
> > > > > -rwxr-xr-x   10 root     root        19412 Jan 29 15:43 chown*
> > > > >
> > > > > [admin@linux11 /]$ chown --version
> > > > > chown (GNU fileutils) 4.0p
> > > > > Written by David MacKenzie.
> > > > >
> > > > > Copyright (C) 1999 Free Software Foundation, Inc.
> > > > > This is free software; see the source for copying conditions.  There is NO
> > > > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> > > > >
> > > > > What could be the problem??
> > > > >
> > > > > many thanks in advance!
> > > > >
> > > > > jimmy
> > > > >
> > > > > am [Wed, 02 May 2001 16:53:30 +0100] schrieb Damion Parry 
><[EMAIL PROTECTED]> :
> > > > >
> > > > > > Hello,
> > > > > >
> > > > > > I've just tried to replicate you're problem, but have had no joy:
> > > > > >
> > > > > > [admin@vsone ftp]$ ls -l
> > > > > > total 4
> > > > > > drwxr-xr-x    2 ftp      ftp          4096 May  2 11:15 incoming
> > > > > > [admin@vsone ftp]$ chown admin incoming/
> > > > > > [admin@vsone ftp]$ ls -l
> > > > > > total 4
> > > > > > drwxr-xr-x    2 admin    ftp          4096 May  2 11:15 incoming
> > > > > > [admin@vsone ftp]$ chown ftp incoming/
> > > > > > [admin@vsone ftp]$ ls -l
> > > > > > total 4
> > > > > > drwxr-xr-x    2 ftp      ftp          4096 May  2 11:15 incoming
> > > > > > [admin@vsone ftp]$
> > > > > >
> > > > > > There may be some problems with the packages installed into you're skel.
> > > > > >
> > > > > > Damion.
> > > > > >
> > > > > >
> > > > > > Stenny wrote:
> > > > > > >
> > > > > > > Dear Ben��
> > > > > > >
> > > > > > >                 I know that I did type the syntax correctly, chown ftp 
>filename, the file I want to change ownership which own by admin, but now I want it 
>own by ftp, so I type.
> > > > > > >
> > > > > > >                 chown ftp filename
> > > > > > >
> > > > > > >                 But it return operation not permitted. Is it VS's admin 
>user cannot change any file's ownership?
> > > > > > >
> > > > > > >                 Thanks you.
> > > > > > >
> > > > > > > Stenny.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > �� 2001-05-02 15:00:00 �����
> > > > > > > >Dear Stenny,
> > > > > > > >
> > > > > > > >You are typing the syntax for chown incorrectly.
> > > > > > > >
> > > > > > > >It goes like this... chown user[.group] filename
> > > > > > > >
> > > > > > > >So in your case you want to do
> > > > > > > >  chown user ftp
> > > > > > > >NOT  chown ftp user
> > > > > > > >
> > > > > > > >Hope this helps,
> > > > > > > >
> > > > > > > >---
> > > > > > > >Ben Kennish
> > > > > > > >[EMAIL PROTECTED]
> > > > > > > >
> > > > > > > >>
> > > > > > > >> Dear,
> > > > > > > >>
> > > > > > > >>         Don't know whether someone have already ask this question, if 
>yes please tell where to find more information.
> > > > > > > >>
> > > > > > > >>         I've login to a vs with admin user, and try to change owner 
>of a file which own by admin to ftp, but it return chown: ftp : operation not 
>permitted.
> > > > > > > >>
> > > > > > > >>         Isn't it admin user can change any file which within the 
>uid-gid range of the vs?
> > > > > > > >>
> > > > > > > >>     Thanks you.
> > > > > > > >>
> > > > > > > >>             Stenny
> > > > > > > >>             [EMAIL PROTECTED]
> > > > > > > >.
> > > > > > >
> > > > > > >                     ��
> > > > > > > ��
> > > > > > >
> > > > > > >             Stenny
> > > > > > >             [EMAIL PROTECTED]
> > > > >
> > > > > James T. Koerting
> > > > >
> > > > > KSD Germany
> > > > > [EMAIL PROTECTED]
> > > > >
> > > > > Murphy's Law: "Anything that can go wrong, will go wrong"
> > > > > Parkinson's Law: "Work expands to exceed available time"
> > > > > Koerting's Law: "Don't fight against these laws"
> > > > ------------------------ The freeVSD Support List -------------------------
> > > > Join:      mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
> > > > Remove:    mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
> > > > Archives:  http://freevsd.org/support/mail-archives/freevsd-support
> > > > ---------------------------------------------------------------------------
> > >
> > > James T. Koerting
> > >
> > > KSD Germany
> > > [EMAIL PROTECTED]
> > >
> > > Murphy's Law: "Anything that can go wrong, will go wrong"
> > > Parkinson's Law: "Work expands to exceed available time"
> > > Koerting's Law: "Don't fight against these laws"
> > ------------------------ The freeVSD Support List -------------------------
> > Join:      mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
> > Remove:    mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
> > Archives:  http://freevsd.org/support/mail-archives/freevsd-support
> > ---------------------------------------------------------------------------
> 
> James T. Koerting
> 
> KSD Germany
> [EMAIL PROTECTED]
> 
> Murphy's Law: "Anything that can go wrong, will go wrong"
> Parkinson's Law: "Work expands to exceed available time"
> Koerting's Law: "Don't fight against these laws"
> ------------------------- The freeVSD Support List --------------------------
> Subscribe:   mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
> Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
> Archives:    http://freevsd.org/support/mail-archives/freevsd-support
> -----------------------------------------------------------------------------
------------------------- The freeVSD Support List --------------------------
Subscribe:   mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
Archives:    http://freevsd.org/support/mail-archives/freevsd-support
-----------------------------------------------------------------------------

Reply via email to