RE: [cobalt-users] CGIWrap

["dlyles" <dlyles@xxxxxxxxxxxxxxxxxxx>]

I didn't see my original reply post.  Anyway, I need the two year old
explanation on how to do this.

-----Original Message-----
From: cobalt-users-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Jelmer Jellema
Sent: Friday, March 01, 2002 6:31 AM
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: Re: [cobalt-users] CGIWrap


?
>
> "The cgiwrap executable(s) were not made setuid-root. This is required for
> it to function properly. (SetUID root is needed in order to change the uid
> to that of the script owner. This is an installation error please make the
> executable setuid root, or use the 'make install' method of installing the
> executables."

[root logs]# ls -l /usr/cgiwrap/
total 172
-rwsr-xr-x   4 root     root        42102 Jun 28  2000 cgiwrap
-rwsr-xr-x   4 root     root        42102 Jun 28  2000 cgiwrapd
-rwsr-xr-x   4 root     root        42102 Jun 28  2000 nph-cgiwrap
-rwsr-xr-x   4 root     root        42102 Jun 28  2000 nph-cgiwrapd

this is how it should be, look at the "s". You could recreate these
permissions by using
chomd u=rwx+s,go=rx FILE
(put the real filename in stead of FILE).

BUT I would be prudent about it. Why are they not SUID in the first place,
they should be on a freshly installed system. So, what happened to them. Are
you sure the are the original files?

go to /usr/cgiwrap
do a:

ls -i

and make sure those 4 files have the same i-node number (the number before
the permissions)

do a:

file cgiwrap

it should give something like:
cgiwrap: setuid ELF 32-bit LSB executable, Intel 80386, version 1,
dynamically linked (uses shared libs), not stripped

If you think everything is ok, you could try and make them setuid

Jelmer



_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users