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

Update openresty to 1.13.6.2 #1623

Merged
merged 1 commit into from
Mar 22, 2019
Merged

Update openresty to 1.13.6.2 #1623

merged 1 commit into from
Mar 22, 2019

Conversation

markan
Copy link
Contributor

@markan markan commented Jan 31, 2019

NOTE: Fix this points to a branch of omnibus-software; point to master before merging.

There are outstanding CVEs against 1.11, so it's time to update.

This breaks PPC/S390 builds; we'll need to figure out a workaround to before we can build for these platforms again.

See 03fce8f for details.

Signed-off-by: Mark Anderson [email protected]

Description

Brings us up to date with OpenResty

Issues Resolved

1.13.6.2 fixes CVE-2018-9230

@markan markan requested a review from a team January 31, 2019 06:15
@markan markan force-pushed the ma/update_openresty branch 2 times, most recently from 292aaaf to b13ec6b Compare February 4, 2019 23:57
@markan
Copy link
Contributor Author

markan commented Feb 6, 2019

This is ready to go once we fix the failing tests in travis.

@markan markan changed the title WIP: Update openresty to 1.13.6.2 Update openresty to 1.13.6.2 Feb 6, 2019
@srenatus
Copy link
Contributor

srenatus commented Feb 6, 2019

This breaks PPC/S390 builds; we'll need to figure out a workaround to before we can build for these platforms again.

Yeah, I was afraid this would happen. What's our plan? 😃

@Annih
Copy link

Annih commented Mar 17, 2019

Being very interested in bumping openresty, I'm curious too to know what is your plan @srenatus & @markan :)

@markan
Copy link
Contributor Author

markan commented Mar 20, 2019

We haven't forgotten about this; we've been rebuilding our build and test pipelines and this has been delayed behind that. This should be able to be merged as soon as #1644 goes in.

@markan markan force-pushed the ma/update_openresty branch 2 times, most recently from c399711 to 0099e05 Compare March 21, 2019 19:28
@markan markan closed this Mar 22, 2019
@markan markan force-pushed the ma/update_openresty branch from 0099e05 to 8305e20 Compare March 22, 2019 17:05
There are outstanding CVEs against 1.11, so it's time to update.

This breaks PPC/S390 builds; we'll need to figure out a workaround to before we can build for these platforms again.

See 03fce8f for details.

Update lpeg as well

Signed-off-by: Mark Anderson <[email protected]>
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.

None yet

3 participants