linux-kernel - Re: Question to directory setgid bit FS implementation details

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]

Message-ID: <6d74828ba3d3350978233ddb54b4fdc0@mail.net4visions.de>
Date:	Tue, 25 Oct 2011 13:57:17 +0200
From:	Markus Kolb <linux-201011@...er-net.de>
To:	<linux-kernel@...r.kernel.org>
Cc:	<Valdis.Kletnieks@...edu>
Subject: Re: Question to directory setgid bit FS implementation details

On Tue, 25 Oct 2011 05:19:24 -0400, Valdis.Kletnieks@...edu wrote:
> On Tue, 25 Oct 2011 10:55:55 +0200, Markus Kolb said:
>
>> can you please explain in brief how the creation of files
>> in directories with setgid bit set is implemented in
>> filesystems.
>
> Look in fs/inode.c, function inode_init_owner(). All of 8 lines of 
> code.

Ok.
Looks for me that there are only changes in data structs.

To be on the safe side can you confirm that there should be no call
inside the kernel code to change the effective group of a process
which creates a file in a directory with setgid-bit set?!

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