hancock

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

Hancock relies on IPFS to distribute data. Running your own IPFS node is
strongly recommended. See http://ipfs.io .

For building hancock, install Go version 1.12 or higher. See
https://golang.org/doc/install .

## Build and Configure

    go get src.d10.dev/hancock/cmd/...
    cp ${GOPATH%:*}/src/src.d10.dev/hancock/cmd/hancock/example/hancock.cfg ~/.config/hancock/hancock.cfg

The file `examples/hancock.cfg` has a reasonable set of defaults. Review the
comments in that file for more information. Copy the example to your
`~/.config/hancock/` and make edits if needed.

## General Usage as author

The hancock command expects optional flags and exactly one operation. Each
operation may expect operation-specific flags or arguments.

    hancock [command flags] operation [operation flags] [operation args]

Each operation produces output to stdout and expects input from stdin, in
................................................................................
Construct a manifest representing a source file with:

    hancock manifest /path/to/source/file [...]

Output is JSON-encoded data about the source file(s), in the format expected
by `hancock-sign`.

## Operation testimony

Publish signed testimony to an index with:









    hancock testimony

The operation expects as input the output of `hancock-sign`.


## Operation verify

Check that a copy of source matches the signed testimony of a trusted
authority.

    hancock verify /path/to/source/copy [...]

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 may be produced by third parties (not exclusively the source
author). Each verifiers independently chooses which authorities they trust.

Testimony is based on a robust hash of source data, in order to guarantee
authenticity while not revealing the original source. Hancock treats all
testimony as public information; although the implementation is currently
limited to finding testimony locally, the ability to store and retreive
testimony from public servers is under development.

The name "hancock" comes from "John Hancock" - a slang term in the United
States meaning a person's signature.

Copyright (C) 2019, 2020 David N. Cohen see source code for license (AGPL 3)

## Dependencies




For building hancock, install a (very) recent version of Go. See
https://golang.org/doc/install .

## Build and Configure

    go get src.d10.dev/hancock/cmd/...






## General Usage As Author

The hancock command expects optional flags and exactly one operation. Each
operation may expect operation-specific flags or arguments.

    hancock [command flags] operation [operation flags] [operation args]

Each operation produces output to stdout and expects input from stdin, in
................................................................................
Construct a manifest representing a source file with:

    hancock manifest /path/to/source/file [...]

Output is JSON-encoded data about the source file(s), in the format expected
by `hancock-sign`.

## Operation publish

Publish signed testimony to an index with:

    hancock publish

This operation published the files produced by `hancock testimony`.

## Operation testimony

Produce signed testimony with:

    hancock testimony

This operation expects as input the output of `hancock-sign`. Testimony is
saved locally, or optionally published to an index.

## Operation verify

Check that a copy of source matches the signed testimony of a trusted
authority.

    hancock verify /path/to/source/copy [...]

//
// 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
//
// Hancock relies on IPFS to distribute data. Running your own IPFS
// node is strongly recommended. See http://ipfs.io .
//
// For building hancock, install Go version 1.12 or higher.  See
// https://golang.org/doc/install .
//
// Build and Configure
//
//    go get src.d10.dev/hancock/cmd/...
//    cp ${GOPATH%:*}/src/src.d10.dev/hancock/cmd/hancock/example/hancock.cfg ~/.config/hancock/hancock.cfg
//
// The file `examples/hancock.cfg` has a reasonable set of defaults.
// Review the comments in that file for more information. Copy the
// example to your `~/.config/hancock/` and make edits if needed.
//
// General Usage as author
//
// The hancock command expects optional flags and exactly one
// operation.  Each operation may expect operation-specific flags or
// arguments.
//
//    hancock [command flags] operation [operation flags] [operation args]
//

//
// 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 may be produced by third parties (not exclusively the
// source author).  Each verifiers independently chooses which
// authorities they trust.
//
// Testimony is based on a robust hash of source data, in order to
// guarantee authenticity while not revealing the original
// source. Hancock treats all testimony as public information;
// although the implementation is currently limited to finding
// testimony locally, the ability to store and retreive testimony from
// public servers is under development.
//
// The name "hancock" comes from "John Hancock" - a slang term in the
// United States meaning a person's signature.
//
// Copyright (C) 2019, 2020  David N. Cohen see source code for license (AGPL 3)
//
// Dependencies
//



// For building hancock, install a (very) recent version of Go.  See
// https://golang.org/doc/install .
//
// Build and Configure
//
//    go get src.d10.dev/hancock/cmd/...

//




// General Usage As Author
//
// The hancock command expects optional flags and exactly one
// operation.  Each operation may expect operation-specific flags or
// arguments.
//
//    hancock [command flags] operation [operation flags] [operation args]
//