I had this problem during a ubuntu update. IIRC: I discovered that the
update changed the user/group id's of mailman from mailman:www-data to
list:list (or something like that) as it did a mailman update that
messed up the id's. It has been too long to remember the exact details.
The defaul
On 3/29/2017 3:08 PM, Nick Wyman wrote:
The setregid call simply returns -1. What is odd is that it is the
wrapper is attempting to set the GID to the current value.
I don't have the linux kernel source handy, but in the freebsd code if the
calling process doesn't have the right credentials,
On 03/29/2017 06:09 PM, Nick Wyman wrote:
>
> Yes, sorry, that was captured when I tried setting the apache gid to 38 (list
> group). Below is the output from standard apache config (running for
> months) with apache gid 33 (www-data).
>
> check_caller: start
> check_caller: end
> run_script:
>
> What group is GID 38?
>
> I would expect the wrapper to see the effective GID is that of "list"
> and the real GID is that of "www-data" and then to be trying to set the
> real GID to be the effective GID.
>
Yes, sorry, that was captured when I tried setting the apache gid to 38 (list
grou
On 03/29/2017 03:08 PM, Nick Wyman wrote:
>
> The setregid call simply returns -1. What is odd is that it is the wrapper
> is attempting to set the GID to the current value. Here is some debugging
> output:
>
> check_caller: start
> check_caller: end
> run_script: start
> effective GID 38
> r
> > Why this would start occurring following an OS update, I
> > don't know. Possibly it is some apparmor config or something similar.
>
> Or SELinux became enabled?
>
I've been able to eliminate apparmor (disabled) and selinux (not installed).
The setregid call simply returns -1. What is od
On 3/29/2017 1:44 PM, Mark Sapiro wrote:
Why this would start occurring following an OS update, I
don't know. Possibly it is some apparmor config or something similar.
Or SELinux became enabled?
z!
--
Mailman-Users mailing list Mailman-Users
On 03/29/2017 12:31 PM, Nick Wyman wrote:
>
> Indeed this is the case. I recompiled the wrapper with this code block
> disabled and the web interface functioned again.
>
> Note that the mailman user and group are "list" while apache runs as user and
> group "www-data".
That is expected. The
Mark,
Thank you for looking.
> The error is "Operation not permitted". My best guess is this is
> occurring at this point in the wrapper
>
> #ifdef HAVE_SETREGID
> status = setregid(getegid(), -1);
> if (status)
> fatal(logident, SETREGID_FAILURE, "%s", strerror(e
On 03/28/2017 08:28 PM, Nick Wyman wrote:
> Hello,
>
> I have an Ubuntu 14.04 server running apache2.4 and mailman. This server has
> been running a few lists with no problems for over a year. After updating
> some Ubuntu packages for security maintenance (unfortunately I don't know all
> tha
Hello,
I have an Ubuntu 14.04 server running apache2.4 and mailman. This server has
been running a few lists with no problems for over a year. After updating some
Ubuntu packages for security maintenance (unfortunately I don't know all that
changed, but apache2 and mailman were unaltered), th
11 matches
Mail list logo
