- 22 Apr, 2017 10 commits
-
-
Will Lahti authored
This CR updates all loggers throughout the code base to use `flogging.MustGetLogger`. This function wraps `logging.MustGetLogger` and tracks the logger modules defined in the system. This enables the ability to set log levels for modules using regular expressions. and make it easy to change the levels for any module and all its submodules with a single command (e.g. gossip, ledger, msp). Change-Id: If5d3229ea2312adb56fc21bfdafbed3d967cf1df Signed-off-by:
Will Lahti <wtlahti@us.ibm.com>
-
Jim Zhang authored
-
Gari Singh authored
-
Gari Singh authored
-
Gari Singh authored
-
Gari Singh authored
When BCCSP serialize EC private and public keys to PEM format, it currently includes "ECDSA" in the header. While this is not illegal, it is incompatible with libraries which expect PKCS8 format. This change only uses PKCS8 for EC keys as most libraries and tools support PKCS1 for RSA. Needed to modify the based asn1 marshaling for EC private keys as the Go implementation includes an optional element which is incompatible with several libraries with the most important being the jsrsasign package used by fabric-node-sdk project Change-Id: I802dcdb28b46bd353efe1ed3868feb78f92e92c9 Signed-off-by:
Gari Singh <gari.r.singh@gmail.com>
-
Srinivasan Muralidharan authored
-
jiangyaoguo authored
Add ChaincodeID to ChaincodeAction, so that we can set it while endorsing proposal (FAB-3329) and validate version (FAB-3330) in committer. Make this minimal CR for following CRs could be committed concurrently. Change-Id: I16f8d8c2c0d06ce7cae155791665f98bb52fe000 Signed-off-by:
jiangyaoguo <jiangyaoguo@gmail.com>
-
Angelo De Caro authored
This change-set does the following: 1. It allows the default MSP implementation to carry information about the OUs to be supported. 2. When an Identity is validated, it is checked that the identity's OUs are compatible with those set at the MSP, meaning that their intersection is not empty. If the MSP does not define any required OU then the check is not performed. Change-Id: If5a59c60f25ee5f40bea4d831ea2d051c24d9f05 Signed-off-by:
Angelo De Caro <adc@zurich.ibm.com>
-
Angelo De Caro authored
This change-set improves the test coverage of the msp/mgmt package Change-Id: Iee1a5b57ce5175adee315d9c7a6041cb1cb33aac Signed-off-by:
Angelo De Caro <adc@zurich.ibm.com>
-
- 21 Apr, 2017 13 commits
-
-
Kostas Christidis authored
-
Gari Singh authored
-
denyeart authored
A stale changeset got merged: https://gerrit.hyperledger.org/r/#/c/7975/ containing code that was incompatible with more recent merges. This changeset fixes it. Change-Id: I5de7054c6967d8b3cc791e5916c1d0cf8ffb9cde Signed-off-by:
denyeart <enyeart@us.ibm.com>
-
Kostas Christidis authored
-
YACOVM authored
Was introduced ~ 4 days ago and it seems that it is too brittle for CI these days. It fails because it sends a message via a gRPC stream and expects the sending to return an error because the stream was supposed to be closed, but sometimes it isn't. Disabling now and it will be revisited soon. Change-Id: I3f6d6861b4b917bacff82ab95d25a9f1738837b1 Signed-off-by:
Yacov Manevich <yacovm@il.ibm.com>
-
Yacov Manevich authored
-
Jonathan Levi (HACERA) authored
-
Christopher Ferris authored
-
denyeart authored
Occasionally CouchDB doesn't respond for (exactly) 30s. This is most often seen in create database calls which happens frequently during unit tests. The default peer behavior was to retry couch after 20s, and therefore these occurrences disrupt unit tests and causes them to fail occasionally. This change will set the peer CouchDB timeout to 35s for now, in order to avoid the retries in the peer avoid the unit test problems. After the root problem in CouchDB is resolved, the default may change back to 20s. Change-Id: Id688e2e137b8354512b6543fc63ad3e59a1040eb Signed-off-by:
denyeart <enyeart@us.ibm.com>
-
Christopher Ferris authored
-
Gari Singh authored
-
Gari Singh authored
With the added security features, peers and orderers need to have admin certs in their local MSPs. Cyrptogen generates certs for admin users but was not placing them in the MSP folder for each of the peer and orderer nodes Change-Id: I6151a2b5d103c4caf38fa636f596674af87ab49f Signed-off-by:
Gari Singh <gari.r.singh@gmail.com>
-
Angelo De Caro authored
The e2e example is failing in the current master because who signs the JoinChannel is not recognized as administrator of the peer. This change-set does the following: 1. It fixes the error, by setting the peer's identity as its own administrator. This is done by copying the peer's certificate into the admincerts folder. This change-set fixes the bug reported at https://jira.hyperledger.org/browse/FAB-3292 Change-Id: If250c0b3b61ee56fd0cfb0da8524dd54d840c639 Signed-off-by:
Angelo De Caro <adc@zurich.ibm.com>
-
- 20 Apr, 2017 17 commits
-
-
Artem Barger authored
There are quite a few gossip related golint warnings produced during the validation. This commit takes care to fix them. Change-Id: I9c224cc7bb709688f2d7ff93d4740472ebea9d3c Signed-off-by:
Artem Barger <bartem@il.ibm.com>
-
Yacov Manevich authored
-
Gari Singh authored
-
Jonathan Levi (HACERA) authored
-
Jonathan Levi (HACERA) authored
-
Kostas Christidis authored
-
Christopher Ferris authored
-
Jonathan Levi (HACERA) authored
-
Jonathan Levi (HACERA) authored
-
Yacov Manevich authored
-
Adnan Choudhury authored
https://jira.hyperledger.org/browse/FAB-2662 Changing the CouchDB dockers used in fabric to use recommended configuration (couchdb local.ini). Include config comments in local.ini stating how to enable user security. Also, making sure that all CouchDB unit-tests follow the same procedure for setting up address and login credentials. Including test comments stating how to run tests against CouchDB with user security enabled. Change-Id: I975d04d757d0371c8db03acf0ddcf92c01c35f8c Signed-off-by:
Adnan Choudhury <adnan.choudhury@itpeoplecorp.com> Signed-off-by:
denyeart <enyeart@us.ibm.com>
-
Binh Nguyen authored
-
Yacov Manevich authored
-
Gari Singh authored
-
Gregory Haskins authored
This patch enhances the cryptogen tool by providing a more flexible configuration and output operation, based on a YAML config file and golang templates. Summary of changes: ------------------------- *) Tool now has two subcommands *) "generate" - This takes the role of the previous top-level command. It gets rid of almost all of the previous command-line switches and replaces them with: -output: specify the output directory. defaults to crypto-config -config: specify the input configuration file. defaults to a configuration similar to before (1 orderer, 2 peer orgs, 1 peer/org *) "showtemplate" - Prints the built-in default template to standard out, suitble for saving/editing for future "generate" sessions. *) CommonName outputs are now much more DNS friendly. For example: we now use "peer3.org1.com" in favor of "peerOrg1Peer3". Users also gain total control over the generation of the CommonNames with various templating facilities. See "cryptogen showtemplate" for more details. Change-Id: I5968a794d4469ada8d3b90e112bdfe93e77c9661 Signed-off-by:
Gregory Haskins <gregory.haskins@gmail.com>
-
Yacov Manevich authored
-
senthil authored
QueryResults (i.e., KV and KeyModification structs) are serialized using gob in the peer and deserialized in golang chaincode shim. As gob encoding is not supported in java, this CR replaces gob with proto (provided that QueryResults are defined as protobuf message -- https://gerrit.hyperledger.org/r/#/c/7687/ ). Change-Id: Ice9133fdc30a59397aa0670050401502150f60f5 Signed-off-by:
senthil <cendhu@gmail.com> Signed-off-by:
Luis Sanchez <sanchezl@us.ibm.com>
-