diff options
| author | Joey Hess <joeyh@joeyh.name> | 2017-05-04 17:14:53 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-05-04 17:14:53 -0400 |
| commit | e8f408e6456ac445c53fe50594ee0effc136f86c (patch) | |
| tree | 746922b9ea4281804821eab2b84a22129d342648 | |
| parent | 4d722cde08ae04dc0f0e5fbbf74f7d62ae3f2679 (diff) | |
| download | debug-me-e8f408e6456ac445c53fe50594ee0effc136f86c.tar.gz | |
mention --verify
| -rw-r--r-- | doc/evidence.mdwn | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/evidence.mdwn b/doc/evidence.mdwn index 1306316..05ab691 100644 --- a/doc/evidence.mdwn +++ b/doc/evidence.mdwn @@ -16,6 +16,10 @@ The important thing is that each message points to the SHA256 hash of a previous message, which builds up a chain. This chain can be verified by simply checking the hashes. +Use `debug-me --verify` to verify a debug-me log file. It will display +any GnuPG keys that signed session keys, and will verify all session key +signatures, and all hashes. + ## graphing debug-me sessions The chain of activities can be visualized by running `debug-me --graphviz |