linux-kernel - Re: [PATCH 1/1] devices cgroup: allow mkfifo

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] [day] [month] [year] [list]

Date:	Sat, 13 Dec 2008 15:09:06 +0800
From:	Li Zefan <lizf@...fujitsu.com>
To:	"Serge E. Hallyn" <serue@...ibm.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, lkml <linux-kernel@...r.kernel.org>,
	stable@...nel.org, Pavel Emelyanov <xemul@...nvz.org>,
	Daniel Lezcano <dlezcano@...ibm.com>
Subject: Re: [PATCH 1/1] devices cgroup: allow mkfifo

>> hm.  I'd looked at your description and decided this was 2.6.29 material.
>>
>> But you think it's for 2.6.28 and even for 2.6.27.  How come?
>>
>> (iow, your changelog sucked :)
> 
> Sorry, I should have put the exchange between Li and I in there.
> (Ouch, and I didn't cc: Li this time!  Sorry, Li.)
> 
> Li thought it was 2.6.27/2.6.27 material.  I thought not, but wanted
> to see what the -stable folks thought.
> 

I was not sure about this.

> This is not a security hole, and since noone has complained before
> it doesn't appear to be too inconvenient.  Until the fix goes
> up, container users can always create the fifos and socks on the
> root image while creating the container, before entering the
> device whitelist.
> 

Now the explanation makes it clear for me, thx. :)


--
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/