[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1266585177.31443.17.camel@thorin>
Date: Fri, 19 Feb 2010 14:12:57 +0100
From: Bernd Petrovitsch <bernd@...rovitsch.priv.at>
To: wzt wzt <wzt.wzt@...il.com>
Cc: Alexey Dobriyan <adobriyan@...il.com>,
linux-kernel@...r.kernel.org, sds@...ho.nsa.gov, jmorris@...ei.org,
eparis@...isplace.org
Subject: Re: [PATCH] LSM: add static to security_ops variable
On Fre, 2010-02-19 at 20:23 +0800, wzt wzt wrote:
> > It's not a barrier, it's garbage. Once you know the adress security_ops
> > ended up at, you simply write to it.
>
> How to find the security_ops address if the variable is static? Would
> you please make an example?
- Find the accessor function (which is surely non-static).
- Find the address where writes the parameter.
Other must decide, if it's more secure (as in "obscure") with the
accessor funtion or not.
Bernd
--
Bernd Petrovitsch Email : bernd@...rovitsch.priv.at
LUGA : http://www.luga.at
--
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