[squid-users] Squid 4.14 : no_suid: setuid(0): (1) Operation not permitted

[Alex Rousskov]

On 2/28/21 9:50 AM, David Touzeau wrote:
> Thanks Alex
> 
> This bug is a really "fog"  while i'm using Debian 10.x
> 
> https://superuser.com/questions/731104/squid-proxy-cache-server-no-suid-setuid0-1-operation-not-permitted
> https://forum.netgate.com/topic/67220/squid3-dev-transparente-con-clamav-64-bit-1a-prueba/2
> 
> Your answers since several years:
> http://www.squid-cache.org/mail-archive/squid-users/201301/0399.html
> https://www.mail-archive.com/search?l=squid-users@squid-cache.org&q=subject:"\[squid\-users\]+Warning+in+cache.log"&o=newest&f=1
> 
> My last discuss on squid 4.13
> https://www.spinics.net/lists/squid/msg93659.html

Thank you for locating these emails. I added some of them to the bug report.


> Many users says there is no impact on helpers and performance as it is
> just a warning...
> 
> Did you confirm it ?

The problem is considered "confirmed" from Bugzilla point of view. I am
not aware of any volunteers addressing the suspected FreeBSD-specific
"warnings due to double drop" problems or triaging non-FreeBSD warnings.

Alex.



> Le 28/02/2021 à 01:58, Alex Rousskov a écrit :
>> On 2/27/21 7:22 PM, David Touzeau wrote:
>>
>>> Hi, regulary i have this error :
>>>
>>> 2021/02/28 01:18:43 kid1| helperOpenServers: Starting 5/32
>>> 'security_file_certgen' processes
>>> 2021/02/28 01:18:43 kid1| WARNING: no_suid: setuid(0): (1) Operation not
>>> permitted
>>>
>>> i have set the setuid permission
>>>
>>> chown root:squid security_file_certgen
>>> chmod 04755 security_file_certgen
>>>
>>> or
>>> chown squid:squid security_file_certgen
>>> chmod 0755 security_file_certgen
>>>
>>> in both cases, squid always claim with "the no_suid: setuid(0): (1)
>>> Operation not permitted"
>> Sounds like bug 3785: https://bugs.squid-cache.org/show_bug.cgi?id=3785
>> That bug was filed many years ago and for a different helper/OS, but I
>> suspect it applies to your situation as well.
>>
>>
>>> How can i fix it ?
>> Unfortunately, I do not know the answer to that question. If it is
>> indeed bug 3785, then its current status is reflected by comment #5 at
>> https://bugs.squid-cache.org/show_bug.cgi?id=3785#c5
>>
>>
>> HTH,
>>
>> Alex.
> 
> 
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
>