On 2/6/2013 11:49 PM, Alex Rousskov wrote:
mos, bug 3763 is not about setuid(0) warnings, although both bugs may have been caused by the same Coverity-inspired motivation to check the return values of system calls.Simone, yes, I think you should report the setuid warning bug. If you do, please note that it appears to be BSD-specific. Thank you, Alex.
I have a case on FreeBSD and it's confirm only on FreeBSD and not linux. What can we do with it? Do we want to handle it? Eliezer
