Re: [cobalt-developers] screwed up file ownership and permissions (raq4)

[Rob Montgomery <Rob@xxxxxxxxxxxxxxxxxx>]

I finally got the time to research rpm's capabilities.  After reading a little
closer, you can do a --dump and get all the data for each file, including
the perms.  I went through and got every package back to the correct
user/group/perms, but still no luck with going to www.mysite.com/admin
and getting authenticated.  I can get into the main server admin site, just
not any virtualserver admin sites.  The username/password for the site
admins works via ssh/telnet/ftp, just not into the cobalt admin web
interface...

The only thing I really found suspicious when checking the rpms was
that 2 files from the frontpage-4.0-3 package are different sizes than
what the rpm thinks they should be. This is what I have:

-rwxr-xr-x   1 bin      bin         79168 Sep 25  2000
/usr/local/frontpage/version4.0/_vti_bin/fpcount.exe
-rwxr-xr-x   1 bin      bin        254300 Sep 25  2000
/usr/local/frontpage/version4.0/exes/_vti_bin/fpcount.exe

Can anyone think of any good reasons why these file sizes would be
different than the rpm thinks it should be?

So anyways, many thanks for getting me looking at rpm to find the
original ownership/perms, but unfortunately it didnt fix my problem...
Maybe I'm barking up the wrong tree. Maybe this problem doesnt
have anything to do with file perms ?  Any other ideas of what might
cause the cobalt web-interface to not accept my authentication?

Thanks,

Rob


Chris Johnson wrote:

>         > From: Rob Montgomery <Rob@xxxxxxxxxxxxxxxxxx>
>         >
>         > [My client] did a chown -R as root and royally screwed
>         > up the machine.
>
>     It isn't pleasant, but you can do
>         % rpm -V -a
>         .
>         .
>         .
>         S.5....T c /etc/printcap
>
>     and get a list of all the files that the RPM database thinks
>     have been modified.  The files that have had their mode bits
>     changes will get a 'M' flag as the second character in the
>     first field.
>
>     So
>         % rpm -V -a | egrep '^.M'
>     Should give you a list of everything that has been changed.
>
>     You can then try to fix things by hand, or look at another
>     Cobalt box for the right value.  You can also grab most of
>     our rpms from
>         ftp.cobaltnet.com/pub/products/
>
>     Be careful about installing rpms to be sure that you don't
>     downrev things.  Use 'rpm -q -f' to get the rpm version, and
>     look for that RPM, either in the product directories, or the
>     updates.
>
>     It seems to me that you should be able to get the target
>     modes from the RPM databases in /var/lib/rpm, but I don't
>     see an easy way other than hacking up a perl script and
>     decyphering the rpm record format.
>
>     cj*