| 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
| ||
|
Message-ID: <20070801132827.355c17e5@the-village.bc.nu> Date: Wed, 1 Aug 2007 13:28:27 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Eugene Teo <eugeneteo@...nel.sg> Cc: linux-kernel@...r.kernel.org, "Kawai, Hidehiro" <hidehiro.kawai.ez@...achi.com>, Neil Horman <nhorman@...driver.com>, Bryan Wu <bryan.wu@...log.com> Subject: Re: [PATCH 1/3] coredump: cleanup documentation for suid_dumpable > > NAK - this feature is actively used and can be set by the sysctl > > interface. The PRCTL fixup was just a bug being fixed. The sysctl > > interface is still relevant. > > Thank you for correcting me. Appreciated. I am not aware that it is still > being actively used. May I know who or which program is using this feature? Not programs - people. When you want to debug a large complex system with multiple setuid applications it can rapidly get quite unpleasant. If you set /proc/sys/kernel/suid_dumpable to 2 and /proc/sys/kernel/core_pattern then it becomes possible to get hold of all the core dumps and debug the system as a whole. The system is not secure in this state but while you are doing that kind of debug on a devel system its usually acceptable. Secondly we don't break userspace interfaces except in extreme cases - proc/sys/kernel/suid_dumpable is a user space interface Alan - 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