diff options
| author | Joey Hess <joeyh@joeyh.name> | 2017-05-02 18:07:27 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-05-02 18:07:27 -0400 |
| commit | e8e389a4bce4f9783ec5a0b57f89843ac00342da (patch) | |
| tree | d6e7d69f89c539b19f88f610fad433f5bc1027d1 /debug-me.1 | |
| parent | 87e0e9cf517d2ca2f9dc1011d1924fb068db78e4 (diff) | |
| download | debug-me-e8e389a4bce4f9783ec5a0b57f89843ac00342da.tar.gz | |
capitalization
Diffstat (limited to 'debug-me.1')
| -rw-r--r-- | debug-me.1 | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -11,13 +11,13 @@ 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. .PP -A debug-me session is logged and signed with the developer's Gnupg +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. .PP 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 +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 @@ -44,7 +44,7 @@ default server. .SH DEVELOPER OPTIONS .IP url Connect to a debug-me session on the specified url, to see and interact -with the user's bug. You need a Gnupg key to use this. +with the user's bug. You need a GnuPG key to use this. .IP "--watch url" Connect to a debug-me session on the specified url and display what happens in the session. Your keystrokes will not be sent to the session. |