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

Override github.com/satori/go.uuid revision for transitive deps #6768

Merged
merged 1 commit into from
Dec 7, 2019

Conversation

danielnelson
Copy link
Contributor

This change is being made to reduce confusion around if Telegraf is affected by satori/go.uuid#73. Neither Telegraf 1.12 or 1.13 are affected by this issue, I have not investigated earlier versions.

Telegraf dropped this library as a direct dependency in 1.13, moving to gofrs. In Telegraf 1.12, we do use the affected library, but only for random partitioning in the kinesis and kafka outputs where randomness is not a security issue.

This library still exists as a transitive dependency for the Microsoft Application Insights output plugin. However, they have worked around this bug in their library and we have had the fix since Telegraf 1.8: https://github.com/microsoft/ApplicationInsights-Go/blob/master/appinsights/uuid.go#L14-L21

At first glance it may also appear that the pgx package uses this library, but we are not using the portion of code that includes it.

Required for all PRs:

  • Signed CLA.
  • Associated README.md updated.
  • Has appropriate unit tests.

While there has been a workaround in place for some time, this change is
being made to reduce confusion around if Telegraf is affected by
satori/go.uuid#73
@danielnelson danielnelson added this to the 1.13.0 milestone Dec 7, 2019
@danielnelson danielnelson merged commit f0b0295 into master Dec 7, 2019
@danielnelson danielnelson deleted the satori-rev branch December 7, 2019 01:22
danielnelson added a commit that referenced this pull request Dec 7, 2019
While there has been a workaround in place for some time, this change is
being made to reduce confusion around if Telegraf is affected by
satori/go.uuid#73

(cherry picked from commit f0b0295)
athoune pushed a commit to bearstech/telegraf that referenced this pull request Apr 17, 2020
…uxdata#6768)

While there has been a workaround in place for some time, this change is
being made to reduce confusion around if Telegraf is affected by
satori/go.uuid#73
idohalevi pushed a commit to idohalevi/telegraf that referenced this pull request Sep 29, 2020
…uxdata#6768)

While there has been a workaround in place for some time, this change is
being made to reduce confusion around if Telegraf is affected by
satori/go.uuid#73
arstercz pushed a commit to arstercz/telegraf that referenced this pull request Mar 5, 2023
…uxdata#6768)

While there has been a workaround in place for some time, this change is
being made to reduce confusion around if Telegraf is affected by
satori/go.uuid#73
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.

1 participant