diff options
Diffstat (limited to 'doc/index.mdwn')
| -rw-r--r-- | doc/index.mdwn | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/index.mdwn b/doc/index.mdwn index 84bc344..14fec93 100644 --- a/doc/index.mdwn +++ b/doc/index.mdwn @@ -20,19 +20,21 @@ 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|evidence]] of what they saw and what they did. So the developer's good reputation is leveraged to make debug-me -secure. +secure. If you trust a developer to ship software to your computer, +you can trust them to debug-me. When you start debug-me without any options, it will connect to a debug-me [[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 +to get them connected to you. Then debug-me will show you their GnuPG key, +who has signed it, and will let you know if they are a known developer +of software on your computer. 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 -will keep most developers honest. +will keep developers honest. <video controls width=400 title="debug-me demo" src="https://downloads.kitenet.net/videos/debug-me/debug-me-demo.webm"></video> <video controls width=400 title="debug-me logs" src="https://downloads.kitenet.net/videos/debug-me/debug-me-logs.webm"></video> |