Agoric opaque box
From Erights
(Difference between revisions)
m (just another minor edit) |
m |
||
| (One intermediate revision not shown) | |||
| Line 2: | Line 2: | ||
It is criticised in [http://www.eros-os.org/~majordomo/e-lang/1075.html Against opaque boxes] | It is criticised in [http://www.eros-os.org/~majordomo/e-lang/1075.html Against opaque boxes] | ||
| + | |||
| + | Reasoning of that post was rebutted on #erights on irc.freenode.org . | ||
| + | |||
| + | The rebuttal was somewhat like this: | ||
| + | The boxes need not to trust each other. Only the developers need to trust an brand of an opaque box. | ||
| + | Therefore what trust between two brands of opaque boxes is inhertenly based on the trust of the developer | ||
| + | that programmed an system that could span them in these brands. | ||
Latest revision as of 01:04, 15 March 2009
The concept is introduced in Agoric Open Systems: Agoric Systems in the Large - Section 6.1.2 Hardware Encapsulation
It is criticised in Against opaque boxes
Reasoning of that post was rebutted on #erights on irc.freenode.org .
The rebuttal was somewhat like this:
The boxes need not to trust each other. Only the developers need to trust an brand of an opaque box. Therefore what trust between two brands of opaque boxes is inhertenly based on the trust of the developer that programmed an system that could span them in these brands.
