Re: write protecting syslog

From: George Greer (greerga@circlemud.org)
Date: 02/25/02


On Mon, 25 Feb 2002, paolo greco wrote:

>From: "George Greer" <greerga@circlemud.org>
>> That's because when you run 'autorun' as root it rotates the logs. So
>> CircleMUD creates a new log owned by root.  Then since you're not root,
>> you can't write to it.
>
>Maybe it would help to set a little check on userid...

I hope the problem isn't common enough to require prevention.

>But what about chrooting circlemud?
>Has this been tried before?

Except root can break out of a chroot() so it doesn't buy anything.  The
only really useful reason to run the MUD as root is to bind to a socket <
1024 but even then you'd drop permissions immediately after opening the
socket (which would be moved up to the first thing ever done).

--
George Greer
greerga@circlemud.org

--
   +---------------------------------------------------------------+
   | FAQ: http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
   | Archives: http://post.queensu.ca/listserv/wwwarch/circle.html |
   | Newbie List:  http://groups.yahoo.com/group/circle-newbies/   |
   +---------------------------------------------------------------+



This archive was generated by hypermail 2b30 : 06/25/03 PDT