| Summary: | <www-client/chromium-74.0.3729.108 version bump has high CVE fixes | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Gentoo Security | Reporter: | wbrana | ||||||||||||||||||
| Component: | Vulnerabilities | Assignee: | Gentoo Security <security> | ||||||||||||||||||
| Status: | RESOLVED FIXED | ||||||||||||||||||||
| Severity: | major | CC: | aliaksei.urbanski, amanzharov, audvare, chromium, dharding, grzegorz.kubiak, herrtimson, hyedad, jasmin+gentoo, jesse, mike, mmk, perfect007gentleman, plevine457, richard, sergeev917, skunk | ||||||||||||||||||
| Priority: | Normal | Keywords: | PullRequest, STABLEREQ | ||||||||||||||||||
| Version: | unspecified | Flags: | stable-bot:
sanity-check+
|
||||||||||||||||||
| Hardware: | All | ||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=684238 https://github.com/gentoo/gentoo/pull/12266 |
||||||||||||||||||||
| Whiteboard: | A2 [glsa+ cve] | ||||||||||||||||||||
| Package list: |
www-client/chromium-74.0.3729.169
|
Runtime testing required: | --- | ||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||
|
Description
wbrana
2019-04-24 14:19:39 UTC
Maintainer(s), please advise if you are ready for stabilization or call for stabilization yourself. It will probably be a while until I can commit a suitable version of chromium. There are multiple build failures with gcc, and I have not been able to find a magic combination of patches to make it work. Why not build it with clang as intended? At least for now gcc folks haven’t broken compatibility with clang, but it may happen with new version. I would like to avoid flipping between toolchains every release, and some people were very unhappy with forced clang. Gentoo contains unsafe web browser because some people don't like clang. Seriously? I'm not going to argue about this anymore. I'll work on this if/when I have time. www-client/chromium-clang? Gentoo Vulnerability Treatment Policy https://www.gentoo.org/support/security/vulnerability-treatment-policy.html Hi Mike Are the required patches in a repo somewhere? I'll quite happily find a combo that works if you're busy I'll see what the Arch folk are doing The build failures I've been seeing in the last few releases had more to do with the C/C++ library than GCC itself (In reply to Mike Lothian from comment #9) Part of the problem is I don't know if the patches exist anywhere or not. It may still be broken upstream. This upstream tracker bug is usually pretty helpful, but I haven't had much luck. https://crbug.com/819294 There was quite a bit of refactoring that happened in the "base" component, so it's hard to tell what is relevant to GCC and also difficult to extract just the necessary parts. Here's my work-in-progress. https://github.com/floppym/gentoo/commits/chromium-74 If you can make this work with either gcc or clang, I would appreciate the help. The Ubuntu and Debian guys have this working. I had a look at what the Ubuntu guys did, they appear to be running Clang with some patches. http://deb.debian.org/debian/pool/main/c/chromium/chromium_74.0.3729.108-1.debian.tar.xz If you can get it working with debians patches, please submit a pull request or attach the necessary files. chromium-74.0.3729.131 version builds with clang just fine.
Maybe the other 2 patches can be dropped too.
Haven't tried gcc.
clang is set via package.env in my case.
--- /usr/portage/www-client/chromium/chromium-73.0.3683.86.ebuild 2019-04-19 20:04:39.612025695 +0300
+++ chromium-74.0.3729.131.ebuild 2019-05-07 21:59:49.719709392 +0300
@@ -139,17 +139,8 @@
"
PATCHES=(
- "${FILESDIR}/chromium-compiler-r7.patch"
"${FILESDIR}/chromium-widevine-r4.patch"
"${FILESDIR}/chromium-fix-char_traits.patch"
- "${FILESDIR}/chromium-73-gcc-0.patch"
- "${FILESDIR}/chromium-73-gcc-1.patch"
- "${FILESDIR}/chromium-73-gcc-2.patch"
- "${FILESDIR}/chromium-73-gcc-3.patch"
- "${FILESDIR}/chromium-73-gcc-4.patch"
- "${FILESDIR}/chromium-73-gcc-5.patch"
- "${FILESDIR}/chromium-73-gcc-6.patch"
- "${FILESDIR}/chromium-73-xdg-current-desktop.patch"
)
pre_build_checks() {
@@ -252,12 +243,15 @@
third_party/crashpad/crashpad/third_party/zlib
third_party/crc32c
third_party/cros_system_api
+ third_party/dav1d
third_party/devscripts
third_party/dom_distiller_js
+ third_party/emoji-segmenter
third_party/fips181
third_party/flatbuffers
third_party/flot
third_party/freetype
+ third_party/glslang
third_party/google_input_tools
third_party/google_input_tools/third_party/closure_library
third_party/google_input_tools/third_party/closure_library/third_party/closure
I tried using the patches from https://sources.debian.org/patches/chromium/74.0.3729.108-1/?page=1 But I ran into the Angle issue (seen in https://bugs.gentoo.org/681870) which I don't think is GCC 9 related but possibly related to my and the reporters setup I'm currently compiling with Clang 9999 with the vaapi patch, I notice there are patches there to get things running with the system libraries too if you're interested The build failed with Clang 9999 FAILED: obj/chrome/browser/ui/ui/tab_strip_model_observer.o clang++ -MMD -MF obj/chrome/browser/ui/ui/tab_strip_model_observer.o.d -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CE=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DCR_CLANG_REVISION=\"354873-1\" -D__STDC_CONSTANT_MACROS -DALLOWED=GLIB_VERSION_2_32 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -DENABLE_IPC_FUZZER -DTOOLKIT_VIEWS=1 -DVK_NO_PRRTTI -DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DLEVELDB_PLATFORM_CHROMIUM=1 -DLEVELDB_PLATFORM_CHROMIUM=1 DUCHAR_TYPE=uint16_t -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX -DJPEG_LIBRARY -DSK_VULKAN_HEADER=\"../../skia/config/SkVulkanConfig.h\" -DSK_VULKAN=1 -DSK_SUPPORT_GPU=1 -DSK_GPU_WORKARODDER -DPERFETTO_BUILD_WITH_CHROMIUM -DPERFETTO_FORCE_DLOG=0 -DI18N_ADDRESS_VALIDATION_DATA_URL=\"https://chromium-i18n.ahim_headers/snappy_shim -I../../third_party/libyuv/include -Igen/shim_headers/libpng_shim -Igen/shim_headers/libwebp_shi_shim -Igen/shim_headers/flac_shim -I../../third_party/protobuf/src -Igen/protoc_out -I../../third_party/protobuf/src -Iveldatabase/src/include -I../../third_party/ced/src -I../../third_party/icu/source/common -I../../third_party/icu/sourceskia/config -I../../skia/ext -I../../third_party/skia/include/c -I../../third_party/skia/include/codec -I../../third_parfects -I../../third_party/skia/include/encode -I../../third_party/skia/include/gpu -I../../third_party/skia/include/pathty/skia/third_party/vulkanmemoryallocator -I../../third_party/skia/src/gpu -I../../third_party/skia/src/sksl -I../../thi8/include -I../../third_party/perfetto/include -Igen/third_party/perfetto/protos -I../../testing/gtest/include -Igen/thihird_party/metrics_proto -I../../third_party/mesa_headers -Igen -Igen -Igen -Igen -I../../third_party/libaddressinput/srs/src/include -I../../third_party/brotli/include -Igen -Igen -Igen -Igen -Igen -fno-strict-aliasing --param=ssp-buffer-sower-dbg-declare=0 -m64 -march=x86-64 -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -no-canonicawing -Wno-unneeded-internal-declaration -Wno-undefined-var-template -Wno-ignored-pragma-optimize -O2 -fno-ident -fdata-sp-compare -Wexit-time-destructors -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/uuid -I/usr/include/glib-2include/nss -I/usr/include/nspr -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -std=c++14 -fno-exceptions -fno-rthrome/browser/ui/ui/tab_strip_model_observer.o ../../chrome/browser/ui/tabs/tab_strip_model_observer.cc:51:22: error: defaulting this default constructor would delete TabStripModelChange::TabStripModelChange() = default; ^ ../../chrome/browser/ui/tabs/tab_strip_model_observer.h:106:28: note: default constructor of 'TabStripModelChange' is im const std::vector<Delta> deltas_; ^ 1 error generated. Created attachment 575526 [details]
Partly Tested ebuild
Ok, so after combining my testing and Alex's work. I've got Chromium 74 running.
Draft ebuild attached.
There's some irregularities in my system. So I'm going to clean some out and do some more QA. For example, I built with clang 8. Not 6 which is what is in stable.
I fixed that default constructor issue locally I've pushed the ebuild with the patches to the FireBurn overlay if you're interested https://github.com/FireBurn/Overlay/commit/ba21c73d3a4bce76e1746433648ca21ca8692a30 The ebuild in the FireBurn overlay fails immediately if libva is not installed. Can we keep libva optional? Created attachment 575558 [details]
Looks like Clang6 won't work without further patches.
Looks like Clang6 isn't viable without patches as well.
Created attachment 575560 [details]
FireBurn build failure.
Hey Mike, I copied your ebuild locally and attempted to build it. I have attached the failure log.
I cleaned my system up a bit to make it similar to a normal system so it should have been a good test case.
(In reply to thesirdmz from comment #21) > Created attachment 575560 [details] > FireBurn build failure. > > Hey Mike, I copied your ebuild locally and attempted to build it. I have > attached the failure log. > > I cleaned my system up a bit to make it similar to a normal system so it > should have been a good test case. @thesirdmz Do first: export CHROMIUM_FORCE_CLANG=yes then you can emerge chromium::FireBurn Here's my env entry:
CC=clang
CXX=clang++
CFLAGS="-O3 -pipe -flto=thin -march=native"
CXXFLAGS="${CFLAGS}"
LDFLAGS="${CFLAGS}"
AR="llvm-ar"
NM="llvm-nm"
RANLIB="llvm-ranlib"
I'll need to look into why building with USE=-vaapi isn't working
Mike (and Mike Gilbert), any thoughts on making the ebuild for 75 (current beta)? https://chromereleases.googleblog.com/2019/05/beta-channel-update-for-desktop_8.html I've added one to my Overlay, I'm compiling it now with Clang 9999 but it takes a while with LTO Feel free to give it a go and report back Compiling now (without LTO). Will report back. FAILED: obj/cc/cc/compositor_frame_reporting_controller.o
clang++ -MMD -MF obj/cc/cc/compositor_frame_reporting_controller.o.d -DCC_IMPLEMENTATION=1 -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1
-DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOU
RCE -D_GNU_SOURCE -DCR_CLANG_REVISION=\"357692-1\" -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATI
ONS_ENABLED=0 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -DENABLE_IPC_FUZZER -DVK_NO_PROTOTYPES -DGL_GLEXT_PRO
TOTYPES -DUSE_GLX -DUSE_EGL -DSK_HAS_PNG_LIBRARY -DSK_HAS_WEBP_LIBRARY -DSK_HAS_JPEG_LIBRARY -DSK_VULKAN_HEADER=\"../../skia/config/SkVulkanConfig.h\" -DSK_VU
LKAN=1 -DSK_SUPPORT_GPU=1 -DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" -DVK_NO_PROTOTYPES -DGOOGLE_PROTOBUF_NO_RTTI -DGOOGLE
_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DUSE_CHROMIUM_ICU=1 -DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IM
PL=ICU_UTIL_DATA_FILE -DUCHAR_TYPE=uint16_t -DLEVELDB_PLATFORM_CHROMIUM=1 -DLEVELDB_PLATFORM_CHROMIUM=1 -I../.. -Igen -Igen/shim_headers/libpng_shim -Igen/shi
m_headers/libwebp_shim -Igen/shim_headers/zlib_shim -I../../third_party/khronos -I../../gpu -Igen/shim_headers/libdrm_shim -I../../third_party/vulkan/include
-I../../third_party/libyuv/include -Igen/shim_headers/re2_shim -Igen/shim_headers/snappy_shim -I../../skia/config -I../../skia/ext -I../../third_party/skia/in
clude/c -I../../third_party/skia/include/codec -I../../third_party/skia/include/config -I../../third_party/skia/include/core -I../../third_party/skia/include/
docs -I../../third_party/skia/include/effects -I../../third_party/skia/include/encode -I../../third_party/skia/include/gpu -I../../third_party/skia/include/pa
thops -I../../third_party/skia/include/ports -I../../third_party/skia/include/utils -I../../third_party/vulkan/include -I../../third_party/skia/third_party/vu
lkanmemoryallocator -I../../third_party/skia/src/gpu -I../../third_party/skia/src/sksl -I../../third_party/skia/modules/skottie/include -I../../third_party/vu
lkan/include -I../../third_party/protobuf/src -Igen/protoc_out -Igen/third_party/metrics_proto -I../../third_party/protobuf/src -I../../third_party/ced/src -I
../../third_party/icu/source/common -I../../third_party/icu/source/i18n -I../../third_party/libwebm/source -I../../third_party/leveldatabase -I../../third_par
ty/leveldatabase/src -I../../third_party/leveldatabase/src/include -I../../third_party/mesa_headers -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-pro
tector -funwind-tables -fPIC -pthread -fcolor-diagnostics -fmerge-all-constants -fcrash-diagnostics-dir=../../tools/clang/crashreports -Xclang -mllvm -Xclang
-instcombine-lower-dbg-declare=0 -m64 -march=x86-64 -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -no-canonical-prefixes -Wall -Wextra
-Wimplicit-fallthrough -Wthread-safety -Wextra-semi -Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing -Wno-unneeded-internal-declara
tion -Wno-undefined-var-template -Wno-ignored-pragma-optimize -fno-omit-frame-pointer -g0 -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautologi
cal-overlap-compare -Wexit-time-destructors -O2 -fno-ident -fdata-sections -ffunction-sections -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -Wno-shor
ten-64-to-32 -std=c++14 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -O2 -pipe -march=native -c ../../cc/scheduler/compositor_frame_reporting_control
ler.cc -o obj/cc/cc/compositor_frame_reporting_controller.o
../../cc/scheduler/compositor_frame_reporting_controller.cc:34:3: error: no matching function for call to 'MakeCheckOpValueString'
DCHECK_NE(reporters_[PipelineStage::kBeginMainFrame],
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../base/logging.h:940:31: note: expanded from macro 'DCHECK_NE'
#define DCHECK_NE(val1, val2) DCHECK_OP(NE, !=, val1, val2)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../base/logging.h:911:29: note: expanded from macro 'DCHECK_OP'
EAT_STREAM_PARAMETERS << (::logging::MakeCheckOpValueString( \
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../base/logging.h:724:18: note: candidate function not viable: no known conversion from 'std::unique_ptr<CompositorFrameReporter>' to 'std::nullptr_t' (aka
'nullptr_t') for 2nd argument
BASE_EXPORT void MakeCheckOpValueString(std::ostream* os, std::nullptr_t p);
^
../../base/logging.h:695:1: note: candidate template ignored: requirement 'base::internal::SupportsOstreamOperator<const std::unique_ptr<cc::CompositorFrameRe
porter, std::default_delete<cc::CompositorFrameReporter> > &, void>::value' was not satisfied [with T = std::unique_ptr<cc::CompositorFrameReporter, std::defa
ult_delete<cc::CompositorFrameReporter> >]
MakeCheckOpValueString(std::ostream* os, const T& v) {
^
../../base/logging.h:708:1: note: candidate template ignored: requirement 'std::is_function<std::unique_ptr<cc::CompositorFrameReporter, std::default_delete<c
c::CompositorFrameReporter> > >::value' was not satisfied [with T = std::unique_ptr<cc::CompositorFrameReporter, std::default_delete<cc::CompositorFrameReport
er> >]
MakeCheckOpValueString(std::ostream* os, const T& v) {
^
../../base/logging.h:719:1: note: candidate template ignored: requirement 'std::is_enum<std::unique_ptr<cc::CompositorFrameReporter, std::default_delete<cc::C
ompositorFrameReporter> > >::value' was not satisfied [with T = std::unique_ptr<cc::CompositorFrameReporter, std::default_delete<cc::CompositorFrameReporter>
>]
MakeCheckOpValueString(std::ostream* os, const T& v) {
^
../../cc/scheduler/compositor_frame_reporting_controller.cc:34:3: error: no matching function for call to 'MakeCheckOpValueString'
I've got chromium 75 working with clang-9999 and pushed to my repo, patched were from arch - chromium-dev (In reply to Mike Lothian from comment #28) > I've got chromium 75 working with clang-9999 and pushed to my repo, patched > were from arch - chromium-dev Successfully built with Clang 8. Great News Everyone! Clang 7.1 appears to have been stabilized. I am currently building 74.0.3729.131 with it and everything is going along smoothly. It has passed all the regular failure points. So in theory it should pass. Created attachment 576244 [details]
Clang7 is a Win
Ok Clang 7.1 which has been stabilized and 74 builds fine with it.
Thanks for testing everyone. I'll try a build with clang this week and hopefully get something pushed. A new stable release is out 74.0.3729.157, which doesn't work with the patches given I'm not sure the vaapi patch is worth it, on my Raven system it just produces garbled output and on my Intel/AMD PRIME desktop it errors out as it uses that hardcoded /dev/dri/renderD128 which is the discrete graphics on my laptop I'm going to look at the code MPV uses to select the currently used FD instead of hard coding it I was able to build 74.0.3729.157 with clang-8 with chromium-deconst.patch https://github.com/FireBurn/Overlay/commit/ba21c73d3a4bce76e1746433648ca21ca8692a30#diff-4f4028433668582ccea798f9d93a9704 Created attachment 576776 [details]
Build log failure chromium-74.0.3729.157
(In reply to Mike Lothian from comment #35) > Created attachment 576776 [details] > Build log failure chromium-74.0.3729.157 You have to use Clang to build. > I'm not sure the vaapi patch is worth it, on my Raven system it just produces garbled output and on my Intel/AMD PRIME desktop it errors out as it uses that hardcoded /dev/dri/renderD128 which is the discrete graphics on my laptop Mike Gilbert, I assume you would go without the VA-API patches? I did use clang using the usual way I do it, an entry in package.env (In reply to Andrew Udvare from comment #36) > Mike Gilbert, I assume you would go without the VA-API patches? Correct. I've put the following ebuilds into my overlay: chromium-74.0.3729.157.ebuild chromium-75.0.3770.38.ebuild Version 75 compiled fine for me with Clang-9999 and Version 74 didn't but Alex confirmed it worked with Clang-8 so I've committed it Created attachment 576976 [details]
Gallium Vaapi Fix
So the reason vaapi wasn't working on my Raven system, was 10bit configs needed to be forced off
So I've got the ebuild creating /usr/share/drirc.d/01-chromium.conf with the necessary bits to force it off
I'm also experimenting with allowing Chromium access to /dev/dri/renderD129 was well as D128 - which hopefully might fix my PRIME issues
Does your VA-API patch work with Nvidia drivers (with x11-libs/libva-vdpau-driver installed)? I did not test this on my setup. Created attachment 577140 [details, diff] enable-vaapi.patch Having tested the chromium-74.0.3729.157 build with vaapi enabled on an nvidia prime setup using x11-drivers/nvidia-drivers-430.14, the current patch doesn't work and emits the following: > [7378:7378:0517/142452.865469:ERROR:vaapi_wrapper.cc(1457)] vaCreateConfig failed VA error: the requested VAProfile is not supported > [7378:7378:0517/142452.865673:ERROR:vaapi_wrapper.cc(850)] Failed to create VaapiWrapper for va_profile: -1 This is a patch based on the one from https://github.com/saiarcot895/chromium-ubuntu-build/blob/master/debian/patches/enable_vaapi_on_linux_2.diff. Using it in place of the current enable-vaapi.patch enabled vaapi on my platform when chromium is run with the "--disable-gpu-sandbox" and "--disable-features=MojoVideoDecoder" flags (provided x11-libs/libva-vdpau-driver was build with the patch from https://github.com/saiarcot895/chromium-ubuntu-build/issues/13#issuecomment-326765168 and the h264ify browser extension is installed). Created attachment 577142 [details, diff]
enable-vaapi.patch
Sorry, wrong patch. This is the one that worked.
I was able to build chromium-74.0.3729.157 with gcc-8.3.0 with the following four patches: https://chromium-review.googlesource.com/c/chromium/src/+/1550366 https://chromium-review.googlesource.com/c/chromium/src/+/1478897 https://chromium-review.googlesource.com/c/chromium/src/+/1550363 https://quiche-review.googlesource.com/c/quiche/+/2403 (applied to net/third_party) However, I did not test if this also works with clang. (In reply to Stephan Hartmann from comment #44) > I was able to build chromium-74.0.3729.157 with gcc-8.3.0 with the following > four patches: > > https://chromium-review.googlesource.com/c/chromium/src/+/1550366 > https://chromium-review.googlesource.com/c/chromium/src/+/1478897 > https://chromium-review.googlesource.com/c/chromium/src/+/1550363 > https://quiche-review.googlesource.com/c/quiche/+/2403 (applied to > net/third_party) > > However, I did not test if this also works with clang. clang-7.1 works with this too. If someone wants to create a pull request with a working patchset, that would be very helpful. amd64 stable The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=12f7137d8a7c20d00b6756d12cbd7b0ec1b36c28 commit 12f7137d8a7c20d00b6756d12cbd7b0ec1b36c28 Author: Stephan Hartmann <stha09@googlemail.com> AuthorDate: 2019-06-16 13:39:08 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2019-06-16 23:34:32 +0000 www-client/chromium: security cleanup Bug: https://bugs.gentoo.org/684272 Package-Manager: Portage-2.3.66, Repoman-2.3.11 Signed-off-by: Stephan Hartmann <stha09@googlemail.com> Signed-off-by: Mike Gilbert <floppym@gentoo.org> www-client/chromium/Manifest | 2 - www-client/chromium/chromium-73.0.3683.75.ebuild | 717 -------------------- www-client/chromium/chromium-73.0.3683.86.ebuild | 718 --------------------- www-client/chromium/files/chromium-73-gcc-0.patch | 108 ---- www-client/chromium/files/chromium-73-gcc-1.patch | 99 --- www-client/chromium/files/chromium-73-gcc-2.patch | 51 -- www-client/chromium/files/chromium-73-gcc-3.patch | 69 -- www-client/chromium/files/chromium-73-gcc-4.patch | 59 -- www-client/chromium/files/chromium-73-gcc-5.patch | 65 -- www-client/chromium/files/chromium-73-gcc-6.patch | 88 --- .../files/chromium-73-xdg-current-desktop.patch | 124 ---- .../chromium/files/chromium-compiler-r7.patch | 176 ----- 12 files changed, 2276 deletions(-) This issue was resolved and addressed in GLSA 201908-18 at https://security.gentoo.org/glsa/201908-18 by GLSA coordinator Aaron Bauman (b-man). |
