From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#38045: IceCat: some codecs don't work without workaround Date: Thu, 16 Jan 2020 01:24:50 -0500 Message-ID: <87pnfj7waa.fsf@netris.org> References: <8aeda3327ffd9a6fe83204486edc25e97ef14d03.camel@disroot.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:42227) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1irycS-0004QR-1g for bug-guix@gnu.org; Thu, 16 Jan 2020 01:27:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1irycQ-0002WK-Nk for bug-guix@gnu.org; Thu, 16 Jan 2020 01:27:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:58882) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1irycQ-0002WC-KQ for bug-guix@gnu.org; Thu, 16 Jan 2020 01:27:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1irycQ-0001CJ-Gu for bug-guix@gnu.org; Thu, 16 Jan 2020 01:27:02 -0500 In-Reply-To: <8aeda3327ffd9a6fe83204486edc25e97ef14d03.camel@disroot.org> Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Jakub =?UTF-8?Q?K=C4=85dzio=C5=82ka?= Cc: 38831-done@debbugs.gnu.org, 38045-done@debbugs.gnu.org Hi Jakub, Jakub K=C4=85dzio=C5=82ka wrote: > I had some problems with video codecs in IceCat 68.3.0-guix0-preview1. > For example, consider this page: http://demo.nimius.net/video_test/. By > default, the videos under the headings H.264 / AAC and MPEG4 don't work > ("No video with supported format and MIME type found."). >=20 > The following steps make the first of these videos work: > 1. Open about:config > 2. Click "I accept the risk!" > 3. Set security.sandbox.content.read_path_whitelist to /gnu/store/ > (the trailing / is important). >=20 > The instructions were originally sketched out in this help-guix > message: > https://lists.gnu.org/archive/html/help-guix/2019-12/msg00150.html >=20 > I believe it would be beneficial to make this a default. >=20 > On IRC, bandali suggested that it would be better to only whitelist the > necessary store subdirectories. I don't know how to gather such a list, > but it it seems like a good idea. Thank you for bringing this to my attention. I agree with Amin Bandali that a more precise whitelist is preferable. Moreover, I was not comfortable whitelisting all of /gnu/store. I'm glad to report that it appears to be sufficient to whitelist the RUNPATH of libavcodec.so, plus the /share/mime/ directory from shared-mime-info. I've implemented this in commit 429c8284d232c3f9fbe3dc87a3da323f3a864c03 and pushed it to 'master'. > I don't know how about:config entries modified by the user behave when > IceCat is updated, but in some of the behaviors I can imagine, the > config entry stops updating, As currently implemented, we now arrange to set the *default* value of 'security.sandbox.content.read_path_whitelist' to an appropriate whitelist. Users who have customized 'security.sandbox.content.read_path_whitelist' to work around this issue should now erase that customization, by right-clicking on its entry in , and clicking on "Reset". It might also be necessary to restart IceCat after doing so. > in which case it would be better to add the paths to some internal > whitelist (I reckon such a whitelist already exists and contains > something like /usr/lib). I agree that it would be preferable, but I wasn't sufficiently motivated to implement it. Feel free to propose a patch. I'm not sure it would make much of a difference in practice though, because the net result for anyone who has customized it to /gnu/store/ will be the same: until they reset their customization, their effective whitelist will be all of /gnu/store/*. What do you think? Anyway, thanks to everyone who contributed to this fix! I'm closing both the older bug (38045) and the more recent duplicate (38831), but feel free to reopen if appropriate. Mark