ByzantineAgreement
NuNu·test

IntrusionResistant

A system is called "intrusion resistant", if it, as a whole, continues to adhere to it's predifined rules even in case of a part of the system components violate these rules (accidentally or by malicious intent).

The aim of intrusion resistance is to counter-ballance for the consequences of continued operation of an embraced device under violation of normaly system-guaranted assumtions (e.g., forged data, access rights).

Known ways to achieve that goal are tamper proofed hardware and systems based on ByzantineAgreement.

Remark: Eventually there is no such thing like tamper proofed hardware, just more complication to do so.



border
last modification: Tue, 02 May 2006 19:29:31 +0200
authors: jfw,
document identifier: A849640f672ed0df0958abc0712110f3c
delivered to public at Fri, 03 Sep 2010 09:21:23 +0200
short comments

rss
pdf :: context view
search

25 Jul 2010SQL
16 Jun 2010BALL
16 Jun 2010CouchDB
16 Jun 2010AskemosServer
07 Mai 2010SystemRequirements
30 Mar 2010ProjectsOnThePlate
30 Mar 2010AskemosResources
30 Mar 2010RSchemeInstall
30 Mar 2010INSTALL
30 Mar 2010ChickenScheme
debug-access.scm
27 Nov 2009subscriber
development
12 Jul 2009test
01 Jul 2009TrustCenter
27 Dez 2008JKomG
27 Dez 2008SQLITE
26 Dez 2008FanOut
26 Dez 2008MIME
NetBSD
NOTE
02 Mai 2006AskemosTopMenu
18 Nov 2008StorageAdaptor
18 Nov 2008PStoreStorageAdapt
18 Nov 2008OperationTips
15 Nov 2008PCRE
04 Nov 2008ProgrammingLanguag
09 Sep 2008RelatedProjects
23 Jul 2008ModuleStructure05
17 Jun 2008NEWS
17 Jun 2008HTML
17 Jun 2008ACM
22 Mai 2008HTTP
22 Mai 2008BOSH
10 Mai 2008AskemosBibliograph
10 Mai 2008JerrysDreamAbstrac
20 Apr 2008XSLT
11 Mar 2008CodingStyle
10 Mar 2008
09 Mar 2008MIMEConverter
BSD
07 Mar 2008XML
06 Mar 2008SRFI
01 Mar 2008RFC4810
01 Mar 2008RFC4998
01 Mar 2008KondratieffWerk
04 Jan 2008service-level
04 Jan 2008NameSpaceDSSSLinde
24 Jun 2004KommunikationsInfr
BOINC



Add