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: <AANLkTinIAKHVYKiILxQZXTr30K_Cr5EZQwRzNpYlLULw@mail.gmail.com>
Date:	Thu, 10 Jun 2010 12:42:27 -0600
From:	Brian Gordon <legerde@...il.com>
To:	Chris Friesen <cfriesen@...tel.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Aerospace and linux

> I do work in telco stuff.  We use ECC RAM, turn on ECC/parity on the
> various buses, enable error-checking in the hardware, etc.

Excellent stuff when you have it. :)

> At higher abstraction levels you can checksum the data being stored and
> validate it when you access it.

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.

> You might start by taking a look at the "edac" code in the kernel.
> Linux in general doesn't normally enable all the fault detection code,
> so you may need to start looking at datasheets.

Thank you for the suggestion.  If the memory device supports EDAC/ECC
then definitely enabling it is a good strategy.
--
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/