Re: [squid-users] WARNING: no_suid: setuid(0): (1) Operation not permitted

On 01/31/2013 03:06 AM, Amos Jeffries wrote:
> On 31/01/2013 10:24 p.m., Simone Levy wrote:
>> Hello there,
>>
>> we are receiving warnings after upgrading squid from version 3.1 to
>> 3.2 on FreeBSD. Squid appears to be fully operational though.
>>
>> The warnings seem to be relative to starting the helpers and opening
>> the log files, but the helpers are started and the log files written to.
>
> When dealing with logs from asynchronous event code things are not
> always as they seem.
> If those are working its most likely not them.
>
> You might have to start Squid under a debugger to find out what
> specifically setuid is being called for.

Amos,

    FWIW, I have seen this warning on FreeBSD as well. Squid calls
set_uid(0) unconditionally. My setuid man page does not mention UID of
zero, and I have not investigated why that call was added, but I have a
feeling that FreeBSD does not like it:

> no_suid(void)
> {
...
> debugs(21, 3, "no_suid: PID " << getpid() << " giving up root priveleges for ever");
>
> if (setuid(0) < 0)
> debugs(50, DBG_IMPORTANT, "WARNING: no_suid: setuid(0): " << xstrerror());

HTH,

Alex.
Received on Thu Jan 31 2013 - 17:03:42 MST