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.

Sign up for GitHub

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

Jump to bottom

Upgrade okhttp to avoid warnings for CVE-2018-20200 #45

Open
renholm opened this issue May 15, 2019 · 2 comments
Open

Upgrade okhttp to avoid warnings for CVE-2018-20200 #45

renholm opened this issue May 15, 2019 · 2 comments
Assignees
@ehrmann @garylee1

Comments

@renholm
Copy link

renholm commented May 15, 2019

We have managed to work around it by managing the dependencies, but we would of course like to avoid that in the long run. Thanks in advance!
@quanpod
Copy link

quanpod commented May 20, 2019

Acknowledging the request - adding @ehrmann / @garylee1

@ehrmann
Copy link
Contributor

ehrmann commented May 21, 2019

We'd actually want to do something like specify the version as 1.+ and pin the version to the oldest-supported version with version locking. This way, we won't start using new features that would break builds for developers, but we'll remove the need to manage some transitive dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ehrmann ehrmann

@garylee1 garylee1

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@renholm @ehrmann @garylee1 @quanpod