Bug#904796: chromium for arm64 lacks security updates
control: tag -1 pending On Tue, Aug 7, 2018 at 9:07 AM, Riku Voipio wrote: > I didn't push this to main stretch branch, as the security upload commit > is reconstructed rather the original from Michael. Changelog hasn't been > updated either. I had forgotten to push after the previous upload, done now. I will include this in the next stable-sec upload. Best wishes, Mike
Bug#904796: chromium for arm64 lacks security updates
On Tue, 7 Aug 2018, Riku Voipio wrote: On Thu, Aug 02, 2018 at 11:53:04PM +, Riku Voipio wrote: The issue seems to be binutils in stable not supporting LR = x30 alias. I've built a fixed version. I'm travelling now, but once I get back, I'll test the fix and submit patch upstream. Similar issue for armhf, but we don't have chromium/armhf on stable, so it's not as important. Fixed branch at: https://salsa.debian.org/chromium-team/chromium/tree/stretch-arm64 I didn't push this to main stretch branch, as the security upload commit is reconstructed rather the original from Michael. Changelog hasn't been updated either. Test binaries at https://people.debian.org/~riku/chromium/ Riku I've installed it and it works. Mikulas
Bug#904796: chromium for arm64 lacks security updates
On Thu, Aug 02, 2018 at 11:53:04PM +, Riku Voipio wrote: > The issue seems to be binutils in stable not supporting LR = x30 alias. I've > built a fixed version. I'm travelling now, but once I get back, I'll test the > fix and submit patch upstream. Similar issue for armhf, but we don't have > chromium/armhf on stable, so it's not as important. Fixed branch at: https://salsa.debian.org/chromium-team/chromium/tree/stretch-arm64 I didn't push this to main stretch branch, as the security upload commit is reconstructed rather the original from Michael. Changelog hasn't been updated either. Test binaries at https://people.debian.org/~riku/chromium/ Riku
Bug#904796: chromium for arm64 lacks security updates
On Thu, 2 Aug 2018, Riku Voipio wrote: tags 904796 + patch upstream thanks On Mon, Jul 30, 2018 at 01:37:57AM +, Riku Voipio wrote: On Sat, Jul 28, 2018 at 05:23:14PM -0400, Michael Gilbert wrote: Chromium on arm64 in Debian Stretch stopped receiving security updates. Chromium for i386, amd64 and armhf received updates for versions 67 and 68, however chromium for arm64 is stuck on version 66. There was a build error in crashpad on arm64 introduced by upstream chromium 67. A patch fixing that has been included with the last two security uploads, so I'm not sure why those builds would have failed. Security build logs are not available, so I missed that. I'll try to reproduce. The issue seems to be binutils in stable not supporting LR = x30 alias. I've built a fixed version. I'm travelling now, but once I get back, I'll test the fix and submit patch upstream. Similar issue for armhf, but we don't have chromium/armhf on stable, so it's not as important. There is "chromium:armhf" version "68.0.3440.75-1~deb9u1" in the Debian Stretch repository. (it doesn't work on arm64, it complains that it can't spawn the GPU process - the 32-bit syscall emulation is likely incomplete) Riku
Bug#904796: chromium for arm64 lacks security updates
tags 904796 + patch upstream thanks On Mon, Jul 30, 2018 at 01:37:57AM +, Riku Voipio wrote: > On Sat, Jul 28, 2018 at 05:23:14PM -0400, Michael Gilbert wrote: > > > Chromium on arm64 in Debian Stretch stopped receiving security updates. > > > Chromium for i386, amd64 and armhf received updates for versions 67 and > > > 68, however chromium for arm64 is stuck on version 66. > > > There was a build error in crashpad on arm64 introduced by upstream > > chromium 67. A patch fixing that has been included with the last two > > security uploads, so I'm not sure why those builds would have failed. > > Security build logs are not available, so I missed that. I'll try to > reproduce. The issue seems to be binutils in stable not supporting LR = x30 alias. I've built a fixed version. I'm travelling now, but once I get back, I'll test the fix and submit patch upstream. Similar issue for armhf, but we don't have chromium/armhf on stable, so it's not as important. Riku description: Stretch binutils doesn't recognize LR on arm64 author: Riku Voipio Index: chromium-browser-68.0.3440.75/third_party/crashpad/crashpad/util/misc/capture_context_linux.S === --- chromium-browser-68.0.3440.75.orig/third_party/crashpad/crashpad/util/misc/capture_context_linux.S +++ chromium-browser-68.0.3440.75/third_party/crashpad/crashpad/util/misc/capture_context_linux.S @@ -312,14 +312,14 @@ CAPTURECONTEXT_SYMBOL2: stp x28, x29, [x0, #0x198] // The original LR can't be recovered. - str LR, [x0, #0x1a8] + str x30, [x0, #0x1a8] // Use x1 as a scratch register. mov x1, SP str x1, [x0, #0x1b0] // context->uc_mcontext.sp // The link register holds the return address for this function. - str LR, [x0, #0x1b8] // context->uc_mcontext.pc + str x30, [x0, #0x1b8] // context->uc_mcontext.pc // NZCV, pstate, and CPSR are synonyms. mrs x1, NZCV
Bug#904796: chromium for arm64 lacks security updates
On Sat, Jul 28, 2018 at 05:23:14PM -0400, Michael Gilbert wrote: > > Chromium on arm64 in Debian Stretch stopped receiving security updates. > > Chromium for i386, amd64 and armhf received updates for versions 67 and > > 68, however chromium for arm64 is stuck on version 66. > There was a build error in crashpad on arm64 introduced by upstream > chromium 67. A patch fixing that has been included with the last two > security uploads, so I'm not sure why those builds would have failed. Security build logs are not available, so I missed that. I'll try to reproduce. Riku
Bug#904796: chromium for arm64 lacks security updates
control: tag -1 confirmed control: severity -1 serious control: found -1 67.0.3396.87-1~deb9u1 control: notfound -1 66.0.3359.117-1~deb9u1 On Sat, Jul 28, 2018 at 2:06 AM, Mikulas Patocka wrote: > Chromium on arm64 in Debian Stretch stopped receiving security updates. > Chromium for i386, amd64 and armhf received updates for versions 67 and > 68, however chromium for arm64 is stuck on version 66. There was a build error in crashpad on arm64 introduced by upstream chromium 67. A patch fixing that has been included with the last two security uploads, so I'm not sure why those builds would have failed. Riki, do you have any ideas? Best wishes, Mike
Bug#904796: chromium for arm64 lacks security updates
Package: chromium Version: 66.0.3359.117-1~deb9u1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I am running Debian Sid on arm64 and use it as a desktop compuer. Chromium on arm64 in Debian Stretch stopped receiving security updates. Chromium for i386, amd64 and armhf received updates for versions 67 and 68, however chromium for arm64 is stuck on version 66. * What exactly did you do (or not do) that was effective (or ineffective)? upgrade debian arm64 system with apt * What was the outcome of this action? chromium is installed at version 66.0.3359.117-1~deb9u1 * What outcome did you expect instead? chromium on arm64 should be upgraded to version 68 just like on the other platforms. *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.5 APT prefers stable APT policy: (500, 'stable') Architecture: arm64 (aarch64) Foreign Architectures: armel, armhf Kernel: Linux 4.17.10 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages chromium depends on: ii libasound2 1.1.3-5 ii libatk1.0-0 2.22.0-1 ii libavcodec57 7:3.2.11-1~deb9u1 ii libavformat577:3.2.11-1~deb9u1 ii libavutil55 7:3.2.11-1~deb9u1 ii libc62.24-11+deb9u3 ii libcairo21.14.8-1 ii libcups2 2.2.1-8+deb9u2 ii libdbus-1-3 1.10.26-0+deb9u1 ii libevent-2.0-5 2.0.21-stable-3 ii libexpat12.2.0-2+deb9u1 ii libflac8 1.3.2-1 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3.2 ii libgcc1 1:6.3.0-18+deb9u1 ii libgdk-pixbuf2.0-0 2.36.5-2+deb9u2 ii libglib2.0-0 2.50.3-2 ii libgtk2.0-0 2.24.31-2 ii libicu57 57.1-6+deb9u2 ii libjpeg62-turbo 1:1.5.1-2 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.12-6 ii libnss3 2:3.26.2-1.1+deb9u1 ii libopus0 1.2~alpha2-1 ii libpango-1.0-0 1.40.5-1 ii libpangocairo-1.0-0 1.40.5-1 ii libpng16-16 1.6.28-1 ii libpulse010.0-1+deb9u1 ii libre2-3 20170101+dfsg-1 ii libsnappy1v5 1.1.3-3 ii libstdc++6 6.3.0-18+deb9u1 ii libvpx4 1.6.1-3+deb9u1 ii libwebp6 0.5.2-1 ii libwebpdemux20.5.2-1 ii libwebpmux2 0.5.2-1 ii libx11-6 2:1.6.4-3 ii libx11-xcb1 2:1.6.4-3 ii libxcb1 1.12-1 ii libxcomposite1 1:0.4.4-2 ii libxcursor1 1:1.1.14-1+deb9u1 ii libxdamage1 1:1.1.4-2+b3 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.1 1.1.29-2.1 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.3-1 ii x11-utils7.7+3+b1 ii xdg-utils1.1.1-1+deb9u1 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages chromium recommends: ii fonts-liberation 1:1.07.4-2 ii libgl1-mesa-dri 13.0.6-1+b2 Versions of packages chromium suggests: pn chromium-driver ii chromium-l10n 66.0.3359.117-1~deb9u1 pn chromium-shell ii chromium-widevine 66.0.3359.117-1~deb9u1 -- no debconf information
