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

sanitize provisioner output strings #23302

Merged
merged 1 commit into from
Nov 6, 2019
Merged

Conversation

jbardin
Copy link
Member

@jbardin jbardin commented Nov 6, 2019

The grpc protocol requires strings to be valid utf8, but because
provisioners often don't have control over the command output, invalid
utf8 sequences can make it into the response causing grpc transport
errors.

Replace all invalid utf sequences with the standard utf replacement
character in the provisioner output. The code is a direct copy from the
go1.13 std library, and can be replaced with strings.ToValidUTF8 once
it's available.

Replaces #22957
Fixes #23300

@jbardin jbardin requested a review from a team November 6, 2019 19:35
@ghost ghost added the sdkv1 [PRs only] Marks changes that may potentially need to be ported to the plugi nSDK label Nov 6, 2019
@jbardin jbardin force-pushed the jbardin/provisioner-utf8 branch from 891d5f5 to 90acdee Compare November 6, 2019 19:42
The grpc protocol requires strings to be valid utf8, but because
provisioners often don't have control over the command output, invalid
utf8 sequences can make it into the response causing grpc transport
errors.

Replace all invalid utf sequences with the standard utf replacement
character in the provisioner output. The code is a direct copy from the
go1.13 std library, and can be replaced with strings.ToValidUTF8 once
it's available.
@jbardin jbardin force-pushed the jbardin/provisioner-utf8 branch from 90acdee to 49439d0 Compare November 6, 2019 19:58
@jbardin jbardin merged commit 2d9d6d7 into master Nov 6, 2019
@jbardin jbardin deleted the jbardin/provisioner-utf8 branch November 6, 2019 20:14
@ghost
Copy link

ghost commented Mar 29, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Mar 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
sdkv1 [PRs only] Marks changes that may potentially need to be ported to the plugi nSDK
Projects
None yet
Development

Successfully merging this pull request may close these issues.

invalid UTF-8 error
2 participants