Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hash volume name to get client token #1041

Merged
merged 1 commit into from
Sep 3, 2021

Conversation

vdhanan
Copy link
Contributor

@vdhanan vdhanan commented Sep 2, 2021

Is this a bug fix or adding new feature?
fixes #1038

What is this PR about? / Why do we need it?
hash the volume name using sha-256 in case the name is longer than 64 characters.

What testing is done?
manually tested that a volume could be created with new token

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Sep 2, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdhanan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 2, 2021
@@ -320,9 +322,12 @@ func (c *cloud) CreateDisk(ctx context.Context, volumeName string, diskOptions *
}
}

// We hash the volume name to generate a unique token that is less than or equal to 64 characters
clientToken := sha256.Sum256([]byte(volumeName))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think encoding is enough here, why do we need extra hashing?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in this step, we are hashing the volumeName, resulting in a byte slice of length 32 (256 bits). in the next step, we hex encode the slice and convert it to a string, ensuring it is always length 64. i think this is the safest way to guarantee we never exceed 64 characters in the token.

@AndyXiangLi
Copy link
Contributor

/lgtm
thanks

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 3, 2021
@k8s-ci-robot k8s-ci-robot merged commit 3b6a45a into kubernetes-sigs:master Sep 3, 2021
k8s-ci-robot added a commit that referenced this pull request Sep 16, 2021
…041-origin-release-1.2

[release-1.2] Automated cherry pick of #1041: hash volume name to get client token
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
3 participants