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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Patch utf8 handling #481

Closed
wants to merge 2 commits into from
Closed

Patch utf8 handling #481

wants to merge 2 commits into from

Conversation

directionless
Copy link
Contributor

@directionless directionless commented May 3, 2019

Osquery sometimes mis-encodes utf8 data osquery/osquery#5288

This is a broad attempt to repair log files that exhibit that issue. This runs against the entire log file. Hopefully, there isn鈥檛 going to be a case where it misfires.

I'm not sure if this is great. On one hand, it fixes a bug in osquery. On the other hand, it introduces a discrepancy between osquery logs and launcher logs. Feel free to vote with 馃憤 or 馃憥. I'm going to let this sit a bit

Fixes: #445

Copy link
Contributor

@zwass zwass left a comment

Choose a reason for hiding this comment

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

My 2c is that the result logs output by Launcher ought to be the same as the result logs put out by osquery (so that Launcher can remain a drop-in replacement).

@directionless
Copy link
Contributor Author

I'm not confident this will behave correctly, and there's one downvote. So I'm going to close this.

@directionless
Copy link
Contributor Author

Sounds like we probably want to revisit this. Probably only triggering repairs on utf8 errors

@directionless directionless restored the seph/utf8 branch August 6, 2020 19:25
@directionless directionless reopened this Aug 6, 2020
Osquery sometimes mis-encodes utf8 data osquery/osquery#5288

This is a broad attempt to repair log files that exhibit that issue. This runs against the entire log file. Hopefully, there isn鈥檛 going to be a case where it misfires.

Fixes: #445
@directionless
Copy link
Contributor Author

In light of the additional conversation on #445, let's revisit this.

This is a pretty heavy handed attempt to repair the data, and failing that, redact it,

I don't have much for a test case though.

@directionless
Copy link
Contributor Author

This was fixed upstream, and I haven't seen this occur in ages. So I'm going to close this PR.

@directionless directionless deleted the seph/utf8 branch July 24, 2023 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

error while marshaling: proto: field \"kolide.agent.LogCollection.Log.Data\" contains invalid UTF-8
2 participants