diff options
| author | Joey Hess <joeyh@joeyh.name> | 2017-04-28 17:09:40 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-04-28 17:09:40 -0400 |
| commit | f4d5ba83fdc484a13809511017989bb401e63c28 (patch) | |
| tree | 54f738eda99e17237d4cc87ae4202124c2b3dac6 /debug-me.cabal | |
| parent | e683f156b7eb8e761c254704538914d86f309801 (diff) | |
| download | debug-me-f4d5ba83fdc484a13809511017989bb401e63c28.tar.gz | |
expand description
Diffstat (limited to 'debug-me.cabal')
| -rw-r--r-- | debug-me.cabal | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/debug-me.cabal b/debug-me.cabal index 329b2a9..7d8cbd7 100644 --- a/debug-me.cabal +++ b/debug-me.cabal @@ -20,6 +20,18 @@ Description: 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. + . + 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. + . + 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. License-File: AGPL Extra-Source-Files: CHANGELOG |