Tags: memekas/fabric-ca
Tags
Release fabric-ca v1.4.5 (hyperledger#94) Signed-off-by: David Enyeart <enyeart@us.ibm.com>
v1.4.3 Release Notes - August 26, 2019 -------------------------------------- What's New in Hyperledger Fabric CA v1.4.3 ------------------------------------------ No new features. Important Fixes --------------- None. Changes, Known Issues, and Workarounds -------------------------------------- Go MySQL driver updated to version 2019-05-10T10:23:35Z. Known Vulnerabilities --------------------- FABC-174 Commands can be manipulated to delete identities or affiliations This vulnerability can be resolved in one of two ways: 1) Use HTTPS (TLS) so that the authorization header is not in clear text. 2) The token generation/authentication mechanism was improved to optionally prevent token reuse. In v1.4 a more secure token can be used by setting environment variable: FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false However, it cannot be set to false until all clients have been updated to generate the more secure token and tolerate FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false. The Fabric CA client has been updated in v1.4 to generate the more secure token. The Fabric SDKs will be updated by v2.0 timeframe to generate the more secure token, at which time the default for Fabric CA server will change to: FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false Resolved Vulnerabilities ------------------------ None. For the full list of improvements and fixes, refer to the release change log: https://github.com/hyperledger/fabric-ca/blob/release-1.4/CHANGELOG.md#v143
v1.4.2 Release Notes - July 17, 2019 ------------------------------------ What's New in Hyperledger Fabric CA v1.4.2 ------------------------------------------ No new features. Important Fixes --------------- FABC-848 create table fails using Postgres with tls Prior to the fix, when using Fabric CA with tls configured for Postres database, the creation of the required tables fails upon initial Fabric CA start. FABC-837 Fabric CA panics when setup for multiple CAs Prior to the fix, Fabric CA would panic upon start if configured for multiple CAs (using --cafiles) and metric gathering. Changes, Known Issues, and Workarounds -------------------------------------- None. Known Vulnerabilities --------------------- FABC-174 Commands can be manipulated to delete identities or affiliations This vulnerability can be resolved in one of two ways: 1) Use HTTPS (TLS) so that the authorization header is not in clear text. 2) The token generation/authentication mechanism was improved to optionally prevent token reuse. In v1.4 a more secure token can be used by setting environment variable: FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false However, it cannot be set to false until all clients have been updated to generate the more secure token and tolerate FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false. The Fabric CA client has been updated in v1.4 to generate the more secure token. The Fabric SDKs will be updated by v2.0 timeframe to generate the more secure token, at which time the default for Fabric CA server will change to: FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false Resolved Vulnerabilities ------------------------ None. For the full list of improvements and fixes, refer to the release change log: https://github.com/hyperledger/fabric-ca/blob/release-1.4/CHANGELOG.md#v142
v1.4.1 Release Notes - April 11, 2019 ------------------------------------- What's New in Hyperledger Fabric CA v1.4.1 ------------------------------------------ FABC-408 Add support for CORS CORS can be enabled in Fabric CA server using new server flags: --cors.enabled Enable CORS for the fabric-ca-server --cors.origins Comma-separated list of Access-Control-Allow-Origin domains FABC-782 Fabric CA API operational metrics FABC-789 Fabric CA database operations metrics FABC-743 Fabric CA health check Changes, Known Issues, and Workarounds -------------------------------------- None. Known Vulnerabilities --------------------- FABC-174 Commands can be manipulated to delete identities or affiliations This vulnerability can be resolved in one of two ways: 1) Use HTTPS (TLS) so that the authorization header is not in clear text. 2) The token generation/authentication mechanism was improved to optionally prevent token reuse. In v1.4 a more secure token can be used by setting environment variable: FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false However, it cannot be set to false until all clients have been updated to generate the more secure token and tolerate FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false. The Fabric CA client has been updated in v1.4 to generate the more secure token. The Fabric SDKs will be updated by v2.0 timeframe to generate the more secure token, at which time the default for Fabric CA server will change to: FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false Resolved Vulnerabilities ------------------------ None. Other improvements and fixes ---------------------------- Updated to Go version 1.11.15 Updated baseimage version to 0.4.15 For the full list of improvements and fixes, refer to the release change log: https://github.com/hyperledger/fabric-ca/blob/release-1.4/CHANGELOG.md#v141
v2.0.0-alpha Release Notes - April 9, 2019 ------------------------------------------ What's New in Hyperledger Fabric CA v2.0 ---------------------------------------- FABC-408 Add support for CORS CORS can be enabled in Fabric CA server using new server flags: --cors.enabled Enable CORS for the fabric-ca-server --cors.origins Comma-separated list of Access-Control-Allow-Origin domains FABC-735 - Docker images with Alpine Linux Hyperledger Fabric CA Docker image will now use Alpine Linux, a security-oriented, lightweight Linux distribution. FABC-782 Fabric CA API operational metrics FABC-789 Fabric CA database operations metrics FABC-743 Fabric CA health check Changes, Known Issues, and Workarounds -------------------------------------- FAB-11096 - Docker images with Alpine Linux Bash is no longer available in Fabric images. Utilize Alpine's built-in sh or ash instead. Known Vulnerabilities --------------------- FABC-174 Commands can be manipulated to delete identities or affiliations This vulnerability can be resolved in one of two ways: 1) Use HTTPS (TLS) so that the authorization header is not in clear text. 2) The token generation/authentication mechanism was improved to optionally prevent token reuse. In v1.4 a more secure token can be used by setting environment variable: FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false However, it cannot be set to false until all clients have been updated to generate the more secure token and tolerate FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false. The Fabric CA client has been updated in v1.4 to generate the more secure token. The Fabric SDKs will be updated by v2.0 timeframe to generate the more secure token, at which time the default for Fabric CA server will change to: FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false Resolved Vulnerabilities ------------------------ None. Other improvements and fixes ---------------------------- Updated to Go version 1.11.5 Updated baseimage version to 0.4.15 For the full list of improvements and fixes, refer to the release change log: https://github.com/hyperledger/fabric-ca/blob/master/CHANGELOG.md#v200-alpha
PreviousNext