Add support for SHA256 fingerprint for diego-ssh #4380
Merged
Conversation
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
Add a new property sha256_fingerprint that diego can use to avoid incompatibilities when updating from sha1 to sha256
1 task
sethboyles
approved these changes
Jun 13, 2025
Samze
approved these changes
Jun 16, 2025
ari-wg-gitbot
added a commit
to cloudfoundry/capi-release
that referenced
this pull request
Jun 18, 2025
Changes in cloud_controller_ng:
- Add support for SHA256 fingerprint for diego-ssh
PR: cloudfoundry/cloud_controller_ng#4380
Author: Sriram Nookala <snookala@vmware.com>
tcdowney
pushed a commit
that referenced
this pull request
Jun 20, 2025
* Add support for SHA256 fingerprint for diego-ssh Add a new property sha256_fingerprint that diego can use to avoid incompatibilities when updating from sha1 to sha256 * Add support for SHA256 fingerprint for diego-ssh Fix rubocop
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Add a new property sha256_fingerprint that diego can use to avoid incompatibilities when updating from sha1 to sha256
Thanks for contributing to cloud_controller_ng. To speed up the process of reviewing your pull request please provide us with:
Add a new property sha256_fingerprint based on the discussion here cloud_controller should emit SHA256 fingerprint for desired lrps for diego-ssh proxy capi-release#539
Snippet of the sample desired_lrps with the new property
"host_fingerprint":"ca:a7:9f:3b:1a:87:78:10:7d:1a:d5:1b:0d:15:83:82:f4:82:52:1d","host_256_fingerprint":"NLHkJb8nhxGcuiJgib46gVPUOt9iS91TQ2+Nd6mvphM="}
An explanation of the use cases your change solves
Links to any other associated PRs
I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
mainbranchI have run all the unit tests using
bundle exec rakeI have run CF Acceptance Tests