lkml.org 
[lkml]   [2003]   [May]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: The disappearing sys_call_table export.
Date
Followup to:  <MDEHLPKNGKAHNMBLJOLKEEFFCOAA.davids@webmaster.com>
By author: "David Schwartz" <davids@webmaster.com>
In newsgroup: linux.dev.kernel
>
> I pointed out to them that any software mechanism I devised for shutting
> the system down would require that they had control over the system in order
> to invoke the mechanism.
>
> They thought about that for a moment and were about to find that the system
> did not meet the requirements. I pointed out that anyone could pull the plug
> or network cable if needed or shut the system down at the switch and that
> this could be accomplished even if they lost control over the system and
> would certainly stop it from sending any information. They then agreed that
> the system met that requirement.
>

"Sometimes it's possible to do in hardware what's impossible to do in
software." Physical access is a powerful discriminator :)

-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:35    [W:0.060 / U:0.468 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site