Small fixes.

Change-Id: Ia9a324500f96118578199d5ced2d01bd0393cbfa
Signed-off-by: joe-alewine <Joe.Alewine@ibm.com>

pull interval must be greater than digestWaitTime + responseWaitTime 
according to core.yaml documentation.
changed mock gossip pull interval value to 4s to make sure it meets the 
requirements.
after the fix ran the test in a loop and haven't seen failures.

Change-Id: Ied5e89cbd8f1d27afcaae93004e289c10b36fe7b
Signed-off-by: nirro <nirro@il.ibm.com>

The godoc of signature.Ver stated that we can check the
value of undisclosed attributes, this should have been
disclosed attributes.

Change-Id: Ideb503f788bd3335cd9bc7505f4310028c59b5b5
Signed-off-by: Manu Drijvers <mdr@zurich.ibm.com>

The path of qscc (github.com/hyperledger/fabric/core/chaincode/qscc) is wrong.

Change it to correct path of github.com/hyperledger/fabric/core/scc/qscc.

Change-Id: Ic70c050c10494a60a2d34f26bc2116d68946e4d7
Signed-off-by: Baohua Yang <yangbaohua@gmail.com>

Change-Id: Icffce261c676fd80afecfeafbc873288c950ffca
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Added links to glossary terms.
Final edits in preparation for +2 review.

Change-Id: Ie2bea8db1ed7bae9a0c8c77e30b2a8c35bde7b32
Signed-off-by: Anthony O'Dowd <a_o-dowd@uk.ibm.com>
Signed-off-by: Chris Gabriel <alaskadd@gmail.com>

Change-Id: Idec22188727673eacce3f91f4ffc0d5e7b44c255
Signed-off-by: Artem Barger <bartem@il.ibm.com>

Add log messages to assist in troubleshouting and debuging of
private data commit and distribution.

Change-Id: I003569d998023a00a6548fdb313e8656f5e6ebd5
Signed-off-by: Artem Barger <bartem@il.ibm.com>

While answering pull message for missing private data we need to
distiguish and choose most recent collection configuration. This commits
adds ledger height while distributing pvt with collection config, hence
while answering pull request we can pick most updated one.

Change-Id: Id50e0e9e8910f33f154cd95f7adc84dc91deb28b
Signed-off-by: Artem Barger <bartem@il.ibm.com>

This CR moves the functions related to pvt data from
the experimental files to the regular files

Change-Id: I0db71f46cc6a5fe5605c227927b5dd2e41585ff7
Signed-off-by: manish <manish.sethi@gmail.com>

Change-Id: I60d1d3c9442167ad5cfe8723bdf11ebabc887e6a
Signed-off-by: joe-alewine <Joe.Alewine@ibm.com>

Any couchdb indexes defined for a chaincode will be deployed in
the chaincode state database.  Indexes for collections of private
data should be applied in the chaincode's collection state database
rather than in the chaincode state database.

Added support for HandleChaincodeDeploy event to common_storage_db.  This
will now process the event from chain code deploy.  The move was necessary
for handling the private data namespace mapping.

Added new function to statecouchdb for processing index creation.

Added new interface to statedb for IndexCapable.  This allows the
common_storage_db to detect that the state database will accept index
creation events.

Updated index validation to allow for indexes under collections directories.

Change-Id: Icfda923c584d953ce5886023f7411bbddb59d595
Signed-off-by: Chris Elder <chris.elder@us.ibm.com>

When doing endorsement, the TxID is checked in
core/common/validation/msgvalidation.go to make sure it equals to
SHA256(nonce+creator).

After that, check whether it is empty again in the core/endorser/endorser.go.
However, the later checking actually won't happen because of the previous validation.

This patchset removed the unused empty checking code.

Change-Id: I99de8e833432200196741b55555d9006f8cb86a0
Signed-off-by: Baohua Yang <yangbaohua@gmail.com>

The collection support in the discovery service supports collections by
filtering out principal sets that aren't authorized by the principals
derived from the policy in the collection config.

This is problematic in cases when the collection config is defined
with principals which have no obvious IsA relation with the
endorsement policy:
Consider a case where the endorsement policy is defined with principals
of Org1.peer or and org2.peer, and the collection is
defined with OUs of Org.

Any principal based policy can't accept nor reject such a scenario,
since a peer role is based on an OU that is hidden from the principal
itself.

This change set moves the filtering to the peer identities instead of
filtering the principal sets of the combinations of the endorsement
policy.

It also raises the code coverage from 97% to 99%

Change-Id: I6d2f9f1e735f667fcffe99c3d3b6bfe6a6ed8e98
Signed-off-by: yacovm <yacovm@il.ibm.com>

The Makefile's 'integration-test' target unnecessarily
builds all the docker images as a dependency. It also
cleans them all, which compounds issues. The only one
it might possibly need is ccenv because the tests
may spin up chaincode.

Also, go test ./... does not correctly handle all tests.
A more correct approach would be to exec go test or ginkgo
from each directory in which there is a suite.

Need to ensure 3rd party images d/l'ed

Change-Id: I8a5c713108c339842471f6415e79924dba7b7964
Signed-off-by: Christopher Ferris <chrisfer@us.ibm.com>

Add changes to add database security to each CouchDB database.   This will
prevent any unauthorized browsing of state data.

Add couchdb methods to expose the CouchDB _security API for PUT and GET to
respectively create and retrieve the database security permissions.

Add the following structure to couchdb to represent the couchdb security
structure:

type DatabaseSecurity struct {
	Admins struct {
		Names []string `json:"names"`
		Roles []string `json:"roles"`
	} `json:"admins"`
	Members struct {
		Names []string `json:"names"`
		Roles []string `json:"roles"`
	} `json:"members"`
}

Add changes to couchdb CreateDatabaseIfNotExist() and apply a security
permission definition based on the configured CouchDB username.  Add the
username to the Admins and Members section.

Change-Id: I8dadd0e1575babef2143c7fb332b863aa0c6be5b
Signed-off-by: Chris Elder <chris.elder@us.ibm.com>

This change set adds integration tests for pluggable endorsement
and validation.

This is actually the e2e but with a slight twist:
The endorsement and validation plugins that are used are actually
not the builtin, compiled ones - but .so plugins that are compiled
at the start of the test.

To ensure that the plugins are run and not the builtin version,
the plugin implementation writes to the file system a file
and the test checks that the file exists after the peers joined the channel.

Change-Id: I69027566f78560ffe9afc03aa9f3f1ac7bdbc6e5
Signed-off-by: yacovm <yacovm@il.ibm.com>

This CR adds validation before allowing an operation on the private data
 - That the collection configuraiton is defined for the chaincode
 - That the collection name exists in the collection config

Change-Id: I3b01bb105e630fde5e350055d1ec19e6d529f5cd
Signed-off-by: manish <manish.sethi@gmail.com>

Also clean them up a bit (formatting,
references to IBM, etc).

Change-Id: I365b16c0a711d54d66c0524340f865ada56b2c21
Signed-off-by: joe-alewine <Joe.Alewine@ibm.com>

Change-Id: I9487d30e8d961dd114f4fb1b76d30c5f36c0283b
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>