linux-kernel - Re: FW: FW: mq

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:	Fri, 06 Aug 2010 12:30:34 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	"Berger\, Lutz \(External\)" <Lutz.Berger.External@...s.com>
Cc:	<linux-kernel@...r.kernel.org>,
	"Denninghoff\, Sven Dr. \(External\)" 
	<Sven.Denninghoff.External@...s.com>,
	"Maehner\, Herbert \(External\)" <Herbert.Maehner.External@...s.com>
Subject: Re: FW: FW: mq_open

"Berger, Lutz (External)" <Lutz.Berger.External@...s.com> writes:

>  
> Hello gentleman,
>
> we have a problem with 
> mq_open, shm_open and sem_open
>
> As stated in the manpage of "open(2)",  the
>   permissions of the created file are (mode & ~umask).
>
> But what is the use of the mode parameter, it it is not used like the programmers intention?
> On HP Unix or TRU64 the mode parameter is not modified.
>
> Could you please check, if this is a bug or a faulty system design on linux? 

Whatever it is -- it would be dangerous to change because suddenly
ignoring umask could add security problems to existing software.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/