linux-kernel - Re: at program breaks with kernel 2.6.24

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1JUS56-0001ur-Tq@faramir.fjphome.nl>
Date:	Wed, 27 Feb 2008 20:36:44 +0100
From:	Frans Pop <elendil@...net.nl>
To:	serge@...lyn.com
Cc:	buraphalinuxserver@...il.com, linux-kernel@...r.kernel.org
Subject: Re: at program breaks with kernel 2.6.24

serge@...lyn.com wrote:
> Quoting BuraphaLinux Server (buraphalinuxserver@...il.com):
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463669
>> 
>> I have the same problem - it is not debian specific.  Did the
>> semantics of kill() change with the new kernel?  I thought as long as
>> something is setuid, even with capability stuff around the setuid
>> programs just get _all_ capabilities and would keep working.
>> 
>> I did a good search and found many people with the problem, but no
>> solutions except going back to 2.6.23.x kernels.  I guess you'll flame
>> me, but at least include a link to the solution too.
> 
> Why would we flame you?  I'll just apologize as I think it's my fault,
> and ask you to please try the newest available kernel where I believe it
> should be fixed.

Would it be this commit that fixed this issue?
commit 094972840f2e7c1c6fc9e1a97d817cc17085378e
Author: Serge E. Hallyn <serue@...ibm.com>
Date:   Sat Feb 23 15:23:33 2008 -0800
    file capabilities: simplify signal check

I see stable was CCed on it, so I guess it will be included in the next
point release, but distributions may want to apply it earlier.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/