Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | edited description and README |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
64a89cc5b7f13b3af20d5dc44ed71bc0 |
User & Date: | dnc 2019-05-23 16:26:14 |
Context
2019-05-23
| ||
16:26 | cmd/hancock: less verbose check-in: 811a5508bb user: dnc tags: trunk | |
16:26 | edited description and README check-in: 64a89cc5b7 user: dnc tags: trunk | |
2019-05-18
| ||
20:06 | bug fix bad logic check-in: 1382961389 user: dnc tags: trunk | |
Changes
Changes to README.md.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
Hancock verifies the authenticity of arbitrary data. The source author produces testimony - a signed attestation - about the source. Verifiers then confirm the authenticity of their copy, using `hancock verify` to compare the copy to testimony. Hancock relies on IPFS to distribute testimony. Testimony includes robust hashes and signatures, to guarantee authenticity while not revealing details about the original source. Testimony may be produced by third parties (not exclusively the source author). Verifiers independently choose which authorities are trusted. The name "hancock" comes from "John Hancock" - a slang term in the United States meaning a person's signature. Copyright (C) 2019 David N. Cohen see source code for license (AGPL 3) ## Dependencies |
| | | < | | > > | |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
Hancock is a tool that proves and verifies the authenticity of files. The source author produces testimony - a signed attestation - about the source. Verifiers then confirm their copy is identical to the souce, using `hancock verify` to test the copy against the testimony. Testimony includes robust hashes and signatures, to guarantee authenticity while not revealing details about the original source. Hancock treats all testimony as public information; currently using IPFS to distribute testimony and a public index service to look up IPFS content identifiers. Testimony may be produced by third parties (not exclusively the source author). Each verifiers independently chooses which authorities they trust. The name "hancock" comes from "John Hancock" - a slang term in the United States meaning a person's signature. Copyright (C) 2019 David N. Cohen see source code for license (AGPL 3) ## Dependencies |
Changes to cmd/hancock/README.md.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
Hancock verifies the authenticity of arbitrary data. The source author produces testimony - a signed attestation - about the source. Verifiers then confirm the authenticity of their copy, using `hancock verify` to compare the copy to testimony. Hancock relies on IPFS to distribute testimony. Testimony includes robust hashes and signatures, to guarantee authenticity while not revealing details about the original source. Testimony may be produced by third parties (not exclusively the source author). Verifiers independently choose which authorities are trusted. The name "hancock" comes from "John Hancock" - a slang term in the United States meaning a person's signature. Copyright (C) 2019 David N. Cohen see source code for license (AGPL 3) ## Dependencies |
| | | < | | > > | |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
Hancock is a tool that proves and verifies the authenticity of files. The source author produces testimony - a signed attestation - about the source. Verifiers then confirm their copy is identical to the souce, using `hancock verify` to test the copy against the testimony. Testimony includes robust hashes and signatures, to guarantee authenticity while not revealing details about the original source. Hancock treats all testimony as public information; currently using IPFS to distribute testimony and a public index service to look up IPFS content identifiers. Testimony may be produced by third parties (not exclusively the source author). Each verifiers independently chooses which authorities they trust. The name "hancock" comes from "John Hancock" - a slang term in the United States meaning a person's signature. Copyright (C) 2019 David N. Cohen see source code for license (AGPL 3) ## Dependencies |
Changes to cmd/hancock/hancock.go.
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 |
// but WITHOUT ANY WARRANTY; without even the implied warranty of // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the // GNU Affero General Public License for more details. // You should have received a copy of the GNU Affero General Public License // along with this program. If not, see <https://www.gnu.org/licenses/>. // Hancock verifies the authenticity of arbitrary data. // // The source author produces testimony - a signed attestation - about // the source. // // Verifiers then confirm the authenticity of their copy, using // `hancock verify` to compare the copy to testimony. // // Hancock relies on IPFS to distribute testimony. Testimony includes // robust hashes and signatures, to guarantee authenticity while not // revealing details about the original source. // // Testimony may be produced by third parties (not exclusively the // source author). Verifiers independently choose which authorities // are trusted. // // The name "hancock" comes from "John Hancock" - a slang term in the // United States meaning a person's signature. // // Copyright (C) 2019 David N. Cohen see source code for license (AGPL 3) // // Dependencies |
| > | | < | | > > > | < > |
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 |
// but WITHOUT ANY WARRANTY; without even the implied warranty of // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the // GNU Affero General Public License for more details. // You should have received a copy of the GNU Affero General Public License // along with this program. If not, see <https://www.gnu.org/licenses/>. // Hancock is a tool that proves and verifies the authenticity of // files. // // The source author produces testimony - a signed attestation - about // the source. // // Verifiers then confirm their copy is identical to the souce, using // `hancock verify` to test the copy against the testimony. // // Testimony includes robust hashes and signatures, to guarantee // authenticity while not revealing details about the original // source. Hancock treats all testimony as public information; // currently using IPFS to distribute testimony and a public index // service to look up IPFS content identifiers. // // Testimony may be produced by third parties (not exclusively the // source author). Each verifiers independently chooses which // authorities they trust. // // The name "hancock" comes from "John Hancock" - a slang term in the // United States meaning a person's signature. // // Copyright (C) 2019 David N. Cohen see source code for license (AGPL 3) // // Dependencies |