summaryrefslogtreecommitdiffhomepage
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joeyh@joeyh.name>2017-05-02 18:12:24 -0400
committerJoey Hess <joeyh@joeyh.name>2017-05-02 18:12:24 -0400
commit3b7b248eaada1bbf71f467c37a5da1196e1bba83 (patch)
tree4479cff3eba0293dcdec9febbef215695cdf4208 /doc
parentf0f263b8018d1d33788eac8ed93f7a1aae1ef5cc (diff)
downloaddebug-me-3b7b248eaada1bbf71f467c37a5da1196e1bba83.tar.gz
links
Diffstat (limited to 'doc')
-rw-r--r--doc/index.mdwn19
1 files changed, 10 insertions, 9 deletions
diff --git a/doc/index.mdwn b/doc/index.mdwn
index 25db3cd..dcf763e 100644
--- a/doc/index.mdwn
+++ b/doc/index.mdwn
@@ -17,17 +17,18 @@ debugging fast, fun, and easy, by letting the developer access your
computer remotely, so they can immediately see and interact with the
problem. Making your problem their problem gets it fixed fast.
-A debug-me session is logged and signed with the developer's GnuPG
-key, producing a chain of evidence of what they saw and what they did.
-So the developer's good reputation is leveraged to make debug-me secure.
+A debug-me session is logged and signed with the developer's GnuPG key,
+producing a [[chain of evidence|evidence]] of what they saw and what they
+did. So the developer's good reputation is leveraged to make debug-me
+secure.
When you start debug-me without any options, it will connect to a debug-me
-server, and print out an url that you can give to the developer to get
-them connected to you. Then debug-me will show you their GnuPG key and who
-has signed it. If the developer has a good reputation, you can proceed
-to let them type into your console in a debug-me session. Once the
-session is done, the debug-me server will email you the signed
-evidence of what the developer did in the session.
+[[server|servers]], and print out an url that you can give to the developer
+to get them connected to you. Then debug-me will show you their GnuPG key
+and who has signed it. If the developer has a good reputation, you can
+proceed to let them type into your console in a debug-me session. Once the
+session is done, the debug-me server will email you the signed evidence of
+what the developer did in the session.
If the developer did do something bad, you'd have proof that they cannot
be trusted, which you can share with the world. Knowing that is the case