Skip to Content.
Sympa Menu

en - Re: [sympa-users] Message::new() Cannot open message file ... Permission

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Simon Taylor <address@concealed>
  • To: address@concealed
  • Subject: Re: [sympa-users] Message::new() Cannot open message file ... Permission
  • Date: Thu, 20 Nov 2008 09:25:23 +1100

Hello again,

OK, I have established that the permissions of the various sympa programs are correct.

I've also set up a test program to ensure that the default apache on Centos doesn't have setuid
disabled in some strange new way I'm not aware of.

When I set up aliases to a setuid and non-setuid instance of my test program as follows:

ScriptAlias /printid_no_setuid /home/sympa/bin/printid_no_setuid
ScriptAlias /printid_setuid /home/sympa/bin/printid_setuid

I get sensible output in my browser:

This is the NON SETUID program
On this server, the sympa user's entry in the passwd file is:
sympa:x:505:502:The sympa mailing list:/home/sympa:/bin/bash
Real UID = 48
Effective UID = 48
Real GID = 48
Effective GID = 48

- and -

This is the SETUID program
On this server, the sympa user's entry in the passwd file is:
sympa:x:505:502:The sympa mailing list:/home/sympa:/bin/bash Real UID = 48
Effective UID = 505
Real GID = 48
Effective GID = 48


So now it looks like I'll have to resort to debugging sympa.pl

- Simon








Archive powered by MHonArc 2.6.19+.

Top of Page