linux-kernel - [PATCH 0/7] fix setuid/setgid clearing in networked filesystems (rev 7)

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

Date:	Thu, 20 Sep 2007 05:10:35 -0400
From:	Jeff Layton <jlayton@...hat.com>
To:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	akpm@...ux-foundation.org
Cc:	linux-cifs-client@...ts.samba.org, nfs@...ts.sourceforge.net,
	ecryptfs-devel@...ts.sourceforge.net,
	reiserfs-devel@...r.kernel.org, unionfs@...esystems.org
Subject: [PATCH 0/7] fix setuid/setgid clearing in networked filesystems (rev 7)

This patchset is the 7th revision for fixing the clearing of setuid and
setgid bits in networked filesystems. It should apply cleanly to
2.6.23-rc6-mm1.

The first four patches in the set are cleanup patches to make sure that
those filesystems don't trip the new BUG() call in notify_change. The
fifth patch (the main one) fixes notify_change to not clear the
ATTR_KILL_S*ID bits when interpreting them into a mode change. The final
two patches change NFS and CIFS to take advantage of the new scheme.

This is basically the same patchset as version 6. The main differences
are changes to ecryptfs and unionfs patches to accomodate changes made
in recent -mm patches. Also, when I sent out the 6th revision I forgot
to mention that the knfsd patch had been changed to more closely reflect
the existing behavior when receiving a setattr call that changes the
mode and uid/gid.

This patchset is being submitted for inclusion into -mm.

Signed-off-by: Jeff Layton <jlayton@...hat.com>
-
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/