| 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: <20120329190922.GG16476@fifo99.com> Date: Thu, 29 Mar 2012 12:09:23 -0700 From: Daniel Walker <dwalker@...o99.com> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: Tim Bird <tim.bird@...sony.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "kernel-team@...roid.com" <kernel-team@...roid.com> Subject: Re: [RFC] Android Logger vs. Shared Memory FIGHT! On Thu, Mar 29, 2012 at 07:50:07PM +0100, Alan Cox wrote: > > The question is whether you are trying to record data for analysis in a > hostile environment or you are trying to do useful debugging. If your > apps are non hostile then PR_SET_NAME is actually useful in logging to > split apart different executions of the same daemon. True.. > The Android logger has no security model of any real kind so it's clearly > about the debug side. In that case the PID lets you correlate with other > logs, the comm data might be useful. Your right it doesn't have much in terms of security, but Tim is suggesting that it is a hostile environment in need of what little security it has. If your logging on a hostile system then Android's logger and my shared memory version are both wide open. However, that doesn't mean you could lock both down in some way. Daniel -- 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