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

Revert "Update EMSDK in net8.0 image" #1285

Merged
merged 2 commits into from
Dec 9, 2024
Merged

Revert "Update EMSDK in net8.0 image" #1285

merged 2 commits into from
Dec 9, 2024

Conversation

sbomer
Copy link
Member

@sbomer sbomer commented Dec 6, 2024

Reverts #1283, see #1283 (comment).

@akoeplinger do you have guidance on addressing #1281? Currently runtime is using a stale image for .NET 8:
https://github.com/dotnet/runtime/blob/c8d152ebbc2c97b6cba580fa8079d4e3b2af1516/eng/pipelines/common/templates/pipeline-with-resources.yml#L101 We need to remove the stale reference, but it's for an image that had version 3.1.34 of the EMSDK.

@akoeplinger
Copy link
Member

None of the vulnerabilities are relevant in our case since we don't run untrusted input and aren't using nodejs in a webserver context. Do you know if we can close them as "won't fix"?

@sbomer sbomer merged commit d75c454 into main Dec 9, 2024
13 checks passed
@MichaelSimons MichaelSimons deleted the revert-1283-updateEMSDK branch December 9, 2024 15:59
@MichaelSimons
Copy link
Member

None of the vulnerabilities are relevant in our case since we don't run untrusted input and aren't using nodejs in a webserver context. Do you know if we can close them as "won't fix"?

I am not familiar with the EMSDK support model. I see the version we are on is well over a year now. Will we be staying on this version for the lifetime of 8.0? This feels like a recipe for numerous vulnerabilities over it's lifetime. Requesting s360 exceptions is not feasible for these. They are going to tell us to update our dependency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants