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
chromium: 60.0.3112.90 -> 61.0.3163.79 [security] #29335
Conversation
@bendlas, thanks for your PR! By analyzing the history of the files in this pull request, we identified @aszlig, @abbradar and @domenkozar to be potential reviewers. |
273b231
to
2773508
Compare
Force pushed with another patch, necessary for building. Build at 80% now. |
With the two commits atop 17.09, the builds failed for me at the very end:
|
swiftshader apparently got integrated recently. trying a build without swiftshader, as per latest patch ... |
pushed another installPhase fix, running another build ... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove that /chromium
from mkdir -p
, otherwise it looks fine.
@@ -12,11 +12,10 @@ mkChromiumDerivation (base: rec { | |||
sandboxExecutableName = "__chromium-suid-sandbox"; | |||
|
|||
installPhase = '' | |||
mkdir -p "$libExecPath/swiftshader" | |||
mkdir -p "$libExecPath/chromium" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just $libExecPath
is enough, because it already contains chromium
, the reason this was $libExecPath/swiftshader
is that mkdir -p
already creates parent directories, which then includes $out/libexec/chromium
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my last build, I had shortened it to mkdir -p "$libExecPath"
, and the installPhase
broke due to that directory missing. I changed it to this version, nix-shell
ed into the --keep-failed
chromium build, ran out=/tmp/out; sandbox=/tmp/sandbox eval "$configurePhase"; eval "$buildPhase"; eval "$installPhase"; fixupPhase
and got, what looked like a good build in /tmp/out
. I'm re-running build now, at [21185/27987]
to verify. I'll probably check back tomorrow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh .. I only saw already contains chromium
now .. that seems fishy ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you're right, I probably interpreted the build error wrong, and it actually broke because of the spurious
, I had left in before: 209b9e8#diff-69a3af1d07b37077e7dd11ccc8f9b61eR15
cp -v "$buildPath/"*.pak "$buildPath/"*.bin "$libExecPath/" | ||
cp -v "$buildPath/icudtl.dat" "$libExecPath/" | ||
cp -vLR "$buildPath/locales" "$buildPath/resources" "$libExecPath/" | ||
cp -v "$buildPath/swiftshader/"*.so "$libExecPath/swiftshader/" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this no longer needed? Does WebGL work for you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, sorry... missed your comment about swiftshader being integrated, nevertheless, please try if WebGL works, because we had that broken a few weeks ago already.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, that cp
broke the build (because the source folder was empty), so I removed it. in research, I found that thing about swiftshader being integrated and it figured. I'll try WebGL, as soon as the build finishes.
pushed fix as per feedback starting another build ... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-tested the default version atop 17.09. All seems OK - including webGL demos/tests.
(cherry picked from commit b82b23b)
Nice :) |
Hmm, I tried to port this to 17.03 but I failed. WIP: https://github.com/vcunat/nixpkgs/commits/p/chromium-17.03 It's possible that the commit works and I'm just repeatedly hitting the Ryzen bug in the particular case. You can try on your machine. |
@bendlas @aszlig I think this change is breaking -cp -v "$buildPath/swiftshader/"*.so "$libExecPath/swiftshader/" It looks like the swiftshader-related But now swiftshader files are never copied, even when they are generated. So headless WebGL in Chromium is broken on NixOS right now. I have a build running to confirm whether it is as I say. |
Interesting. That must have been the time, the flag was defaulted to Thanks for digging this one out. I hope your build succeeds! |
@bendlas Can confirm, the build succeeds with The graphics look a little off/corrupted when swiftshader is used vs my normal GPU, but that's an upstream problem, not a nixpkgs problem. So I think we should thange the derivation to copy exactly when I'll file a new issue to track this (edit: #41918). |
Motivation for this change
security update, please backport
CVE-2017-5111
CVE-2017-5112
CVE-2017-5113
CVE-2017-5114
CVE-2017-5115
CVE-2017-5116
CVE-2017-5117
CVE-2017-5118
CVE-2017-5119
CVE-2017-5120
includes #28857
Things done
Building right now, at about 60%
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)