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
| ||
|
Date: Fri, 8 Aug 2008 04:50:49 +0400 From: Alexey Dobriyan <adobriyan@...il.com> To: Daryl Tester <dt-lkml@...dcraftedcomputers.com.au> Cc: Sven Wegener <sven.wegener@...aler.net>, lkml <linux-kernel@...r.kernel.org> Subject: Re: PROBLEM?: "permission denied" when accessing /proc/self/fd/* after setuid On Fri, Aug 08, 2008 at 10:08:21AM +0930, Daryl Tester wrote: >>> The above environment isn't necessary to replicate the problem, although >>> what stdout and stderr are attached to has some effect. The attached C >>> code replicates the issue, but appears to not fail (that is, succeed) if >>> /proc/self/fd/2 is a terminal (e.g. /dev/pts/X) *and* that terminal is >>> owned by the same uid that the code uses (in this case, 500). In the >>> case of an anonymous pipe it appears to fail consistently as the pipe is >>> owned by root. Something similar was fixed in 2.6.22, but let me check. -- 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/
Powered by blists - more mailing lists