Harness the power of signify(1) to sign arbitrary git objects
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

update readme

+3 -3
+3 -3
README.md
··· 69 69 70 70 The entry `object` is a pointer to the respective git object being 71 71 signed over, which typically assumes the form of a commit object. 72 - On the other hand, `signature` contains the base64 encoded `signify` or 73 - `minisign` signature over the raw (20 byte) id of `object`. The remaining 74 - blobs, `version` and `algorithm`, represent the current version of the 72 + Then, `signature` contains the base64 encoded `signify` or `minisign` 73 + signature over the raw (20 byte) id of `object`. The remaining blobs, 74 + `version` and `algorithm`, represent the current version of the 75 75 `git-signify` tree format and the algorithm (`minisign` or `signify`) 76 76 being used, respectively. 77 77