Conversation
This commit introduces a new configuration option for the hash scheme to use when signing zone keys for server-to-server and clerver-to-server authentication. The hash scheme used historically for signing zone keys is MD5. In order to support deployments with FIPS 140-2 compliance requirements, this configuration was introduced to avoid MD5 usage. The configuration is called zone_key_signing_hash_scheme and can be one of two values: md5 (default) or sha256. The configuration should be added to server_config.json and must have the same value for all servers in a zone. The configuration is not added to the server configuration on upgrade and defaults to the historical MD5 usage if it is absent. The configuration can also be set for servers with which any given server federates. It has the same name and set of accepted values as the local zone configuration. The servers on each side of the federation must use the same hash scheme when signing the zone keys.
This file contains hidden or 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
1 participant
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.
No description provided.