On Wed, March 21, 2007 10:15, Tasos Parisinos wrote: > Protecting a TripleDES key in high security standards is not as > simple as making the kernel read > protected, you need a whole lot and > that also means hardware (cryptomemories e.t.c) > So you forget about all this overhead when you use assymetric
Ah, you're talking about fishing the key out of RAM here, right? My point stays the same for that: If you can't read protect the kernel RAM, small chance you can write protect it. And then they can just bypass all signature checking you put in it anyway. Greetings, Indan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/