On 10/11/2013 08:54 PM, Paul Walmsley wrote:
On Thu, 10 Oct 2013, Tero Kristo wrote:
On 10/09/2013 09:59 PM, Paul Walmsley wrote:
Eh, one correction:
On Wed, 9 Oct 2013, Paul Walmsley wrote:
We could easily wind up with kernels that won't boot at all when used
with newer DT data.
This is a misstatement of the issue: the concern here is that newer
kernels may not boot at all with older DT data - which could easily be in
locked areas of the flash or firmware.
I wonder who would be crazy enough to put DT data into a locked area, and to
what purpose. If you can update the kernel, there is no point locking down DT
data, this will just cause you unnecessary misery.
The DT data will be used by bootloaders also :-(
In situations where the bootloaders are signed and locked, the security
people are also insisting that the DT data be signed and locked.
Well, even if you sign something, you can still update it. Writing any
software to true OTP memory is one way to commit suicide IMO. How many
nasty bugs have you seen with ROM code? Also, if people want to make
their custom security solutions which are not supported by the kernel,
why should the kernel care about it? We don't know the details, and
can't influence the design, so we can't prepare for it anyway.
-Tero
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
