Just a small point about terminology:

The bit you are talking about is not called the "sticky bit".  The name
of the bit in question is the "setuid bit".  This setuid bit the one
that shows up as an "s" in ls listings and which is set via the "+s"
option in chmod.

The "sticky bit" is the one that shows up as a "t" in ls listings and is
set via the "+t" option to chmod, and it has a different purpose than
that of the setuid bit.

>From "man chmod":

  r       The read bits.
  s       The set-user-ID-on-execution and set-group-ID-on-execution 
          bits.
  t       The sticky bit.
  w       The write bits.
  x       The execute/search bits.
  X       The execute/search bits if the file is a directory or
          any of the execute/search bits are set in the original
          (unmodified) mode.  Operations with the perm symbol ``X''
          are only meaningful in conjunction with the op symbol ``+'',
          and are ignored in all other cases.
  u       The user permission bits in the mode of the original
          file.
  g       The group permission bits in the mode of the original
          file.
  o       The other permission bits in the mode of the original
          file.


dax2 <[EMAIL PROTECTED]> writes:

>     Dear Courier List writers!
>
>     Tell the newbies that the webadmin binary is a small front which
> needs the setuid bit in order for it to run the "real stuff" with
> the right permissions. Obvious! And then again?
>
>     This is perhaps as stupid as every other newbie comment. I was
> impressed about courier and have written a small presentation about
> getting it up and running but left out webadmin.
>
>     Later I wanted webadmin to run and got "Invalid password".
>
>     The list here gave the answer - I should have known, of
> course, but I thought that webadmin would run as small
> underprivileged front for the scripts doing the job and thought
> that ./cgi-bin/webadmin wouldn't need the (dangerous) sticky bit
> then.
>
>     The comment below helped me get that straightened! Fine -
> so fine, works so well, I am happy!!!
>
>     Thanks for a fine list and a superb mail server.
>
>
>     Donald Axel
>
>
>
>
>> # From: Stuart Wells
>> # Subject: [courier-users] re: Courier Webadmin
>> # Date: Fri, 16 Apr 2004 12:33:29 -0700
>> 
>>   I ran into the exact same problem last night when I
>> did a build of courier on a slackware 9.1 box.  I'm a
>> newbie as well, and I had misread the install
>> instructions, do the configure, make and make check as
>> non-root and the make install as root.  (I had only
>> done the configure as non-root before).  When I copied
>> the webadmin file over to the cgi-bin directory, I
>> also noticed that it lost the sticky bit - you should
>> be able to fix that (as root) by running ' chmod +s
>> webadmin ' in your cgi-bin directory.
>> 
>>   Hope this helps!  I got webadmin working fairly
>> easily, however... 
>
>   [... cut ...]
>
>
> -- 
> dax2-tele2adsl:dk -- d-axel.dk/  Donald Axel
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> courier-users mailing list
> [EMAIL PROTECTED]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
>

-- 
 Lloyd Zusman
 [EMAIL PROTECTED]
 God bless you.



-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to