| 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: <20081219195311.81C4AFC351@magilla.sf.frob.com> Date: Fri, 19 Dec 2008 11:53:11 -0800 (PST) From: Roland McGrath <roland@...hat.com> To: Hidehiro Kawai <hidehiro.kawai.ez@...achi.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, linux-kernel@...r.kernel.org, yumiko.sugita.yf@...achi.com, satoshi.oshima.fk@...achi.com Subject: Re: [PATCH] coredump_filter: enable to change the default filter > It makes sense. It also enables us to change coredump_filter for > user mode helpers after the system was booted. Right. > However, we would need a special care for PID namespace if we use > init's coredump_filter as default. For a process with new PID > namespace and new /proc, writing to /proc/1/coredump_filter doesn't > mean changing default, although it's not a usual operation. I'd figured that private PID namespaces with their own init would want their own private settings for this default too. > The reason why I suggested the boot parameter way is most users > can change the default easily. Some users have difficulty to > change init scripts for various reasons. I don't object to it deeply or anything. I just pointed out that we do already have an alternative. Thanks, Roland -- 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