linux-kernel - Re: Aerospace and linux

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C113BC2.6070000@libero.it>
Date:	Thu, 10 Jun 2010 21:23:46 +0200
From:	Massimiliano Galanti <massiblue@...ero.it>
To:	Brian Gordon <legerde@...il.com>,
	Chris Friesen <cfriesen@...tel.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Aerospace and linux


> What about .ro and .text sections of an executable?   I would think
> kernel support for that would be required.   If its application data,
> then all sorts of things are possible like you described.   Ive also
> seen critical ram variables be stored in triplicate and then
> compared/voted just to ensure no silent SEU corruption.

Maybe slightly off topic but... if flash is safer than ram, what about 
using XIP (where possible, e.g. on NORs)? That would not put .data 
sections into ram, at least.

-- 
Massimiliano
--
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/