Adds v1.5.6-beta2 release notes #344
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Josh Kneubuhl [email protected]
Release Note
v1.5.6-beta2 Release Notes - Dec 15, 2022
v1.5.6-beta2 is a beta release, providing updates for the following issues in the Fabric CA:
buildxDependencies
Fabric CA v1.5.6 has been tested with the following dependencies:
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:
Use HTTPS (TLS) so that the authorization header is not in clear text.
The token generation/authentication mechanism was improved to optionally prevent
token reuse. As of 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.