Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: git-integration.md - fix what the signature actually signs #142

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 9 additions & 7 deletions doc/git-integration.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,13 +64,15 @@ A signed Git commit adds a ASCII-armored PGP signature:
What the signature actually signs is simply the commit minus the signature
itself; in the above example the exact data the signature signs is:

$ git cat-file -p a9d1ffc2e10dafcf17d31593a362b15c0a636bfc
tree 548b1c88f537cd9939edeea094bfaff094f20874
parent 53c68bc976c581636b84c82fe814fab178adf8a6
author Peter Todd <[email protected]> 1432826886 -0400
committer Peter Todd <[email protected]> 1432827857 -0400

Add working ots command line utility
```
tree 548b1c88f537cd9939edeea094bfaff094f20874
parent 53c68bc976c581636b84c82fe814fab178adf8a6
author Peter Todd <[email protected]> 1432826886 -0400
committer Peter Todd <[email protected]> 1432827857 -0400

Add working ots command line utility

```

You can verify this yourself manually with a bit of cut-and-pasting.
Interestingly, if you ask GnuPG to verify a ASCII-armored signature with
Expand Down