summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGNU Hurd wiki engine <web-hurd@gnu.org>2007-08-19 13:09:13 +0000
committerGNU Hurd wiki engine <web-hurd@gnu.org>2007-08-19 13:09:13 +0000
commitd7da7a87ef7ffa33290c70764dc36a83e985d99e (patch)
tree5fdf2aa67e394a3de0f9547f84c775a8d3ff2afd
parentd318d707f20f7a94f70b056037e08717ab0fbf28 (diff)
web commit by NealWalfield: Create
-rw-r--r--trust.mdwn15
1 files changed, 15 insertions, 0 deletions
diff --git a/trust.mdwn b/trust.mdwn
new file mode 100644
index 00000000..fe2ca5f0
--- /dev/null
+++ b/trust.mdwn
@@ -0,0 +1,15 @@
+The word trust is used in a number of contexts with different technical meanings.
+Sometimes it is used to confuse, for instance trusted computing is rarely about
+providing users reason to trust that software they are running does not violate
+their intents but about providing a mechanism for a third party to verify
+that software that runs on a remote computer obeys him or her rather than the
+user.
+
+When we say that a program trusts another, we mean that [[correctness]] of the
+former depends on the cooperation of the latter. For instance, when a user runs
+ssh, the user's intention is that all communication is encrypted. In this case,
+the user trusts that the ssh binary respects this intent. In Unix, a program's
+[[trusted computing base]] consists not only of the kernel (and all the drivers,
+file systems and protocol stacks that it contains) but every program running
+under the same UID; it is impossible to protect against
+[[destructive interference]] from programs running under the same UID.