about summary refs log tree commit diff
path: root/pkgs/applications/networking/browsers
Commit message (Collapse)AuthorAge
* flashplayer: 32.0.0.371 -> 32.0.0.387taku02020-06-14
|
* firefox-beta-bin: 77.0b7 -> 78.0b2 (security)ajs1242020-06-12
| | | | PR #89438.
* firefox-esr-68: 68.8.0esr -> 68.9.0esr (security)ajs1242020-06-12
| | | | PR #89438.
* firefox-bin: 76.0 -> 77.0.1 (security)ajs1242020-06-12
| | | | PR #89438.
* treewide: use ffmpeg_3 explicitly if not wanted otherwiseDoron Behar2020-06-12
| | | | | | After making `ffmpeg` point to the latest `ffmpeg_4`, all packages that used `ffmpeg` without requiring a specific version now use ffmpeg_3 explicitly so they shouldn't change.
* Merge pull request #89931 from OPNA2608/update-palemoon-28.10.0Anderson Torres2020-06-12
|\ | | | | palemoon: 28.9.3 -> 28.10.0
| * palemoon: 28.9.3 -> 28.10.0Christoph Neidahl2020-06-07
| |
* | chromium{Beta,Dev}: Fix the buildsMichael Weiss2020-06-10
| | | | | | | | Fix #89615.
* | chromiumBeta: Fix the configuration phaseMichael Weiss2020-06-09
| | | | | | | | | | The changes from chromiumDev (see 029a5de0839) are required for chromiumBeta as well.
* | Merge pull request #89565 from jsravn/enable-chromium-rtc-use-pipewireFlorian Klink2020-06-07
|\ \ | |/ |/| chromium: add rtc_use_pipewire
| * Add pipewire to runtime pathJames Ravn2020-06-06
| |
| * chromium: add rtc_use_pipewireJames Ravn2020-06-05
| | | | | | | | | | | | | | | | | | | | | | | | This provides the browser flag #enable-webrtc-pipewire-capturer, which adds support for screensharing on Wayland via xdg-desktop-portal. The browser flag is disabled by default until a user enables it. At least one other major distribution (Arch) enables this compile time option, and so I believe it should be safe to enable by default. This is also needed to support xdg-desktop-portal-wlr which was added in https://github.com/NixOS/nixpkgs/pull/83485.
* | chromiumDev: Fix the configuration phaseMichael Weiss2020-06-06
| | | | | | | | | | | | | | | | | | | | | | | | Relevant changes in M85: - Upstream switched from YASM to NASM [0]. - third_party/binutils was removed [1]. Note: The gn and dev channel updates are optional. cc #89615. [0]: https://bugs.chromium.org/p/chromium/issues/detail?id=766721 [1]: https://github.com/chromium/chromium/commit/9869e86fd9079a6ab4ea23aa03d724580678b356
* | Merge pull request #88050 from squalus/ungoogled-0518Lassulus2020-06-06
|\ \ | | | | | | ungoogled-chromium: 81.0.4044.122-2 -> 81.0.4044.138-1
| * | ungoogled-chromium: 81.0.4044.122-2 -> 81.0.4044.138-1squalus2020-05-18
| | |
* | | chromiumBeta: Fix the source hashMichael Weiss2020-06-06
| |/ |/| | | | | | | For some reason the hash from 9ec139b6725 became invalid, see #89615. The update script does now produce the correct hash.
* | chromium: 83.0.4103.61 -> 83.0.4103.97Michael Weiss2020-06-04
| | | | | | | | | | | | | | | | https://chromereleases.googleblog.com/2020/06/stable-channel-update-for-desktop.html This update includes 5 security fixes. CVEs: CVE-2020-6493 CVE-2020-6494 CVE-2020-6495 CVE-2020-6496
* | Merge pull request #87868 from OPNA2608/update-palemoonChristoph Hrdinka2020-06-04
|\ \ | | | | | | palemoon: 28.9.1 -> 28.9.3
| * | palemoon: 28.9.1 -> 28.9.3Christoph Neidahl2020-05-15
| | |
* | | falkon: use wrapQtAppsHook (#89375)JosephTheEngineer2020-06-03
| | |
* | | tor-browser-bundle-bin: 9.0.9 -> 9.5Emery Hemingway2020-06-03
| | |
* | | qutebrowser: 1.11.1 -> 1.12.0josephtheengineer2020-06-02
| | |
* | | Merge pull request #87277 from CheariX/brave-1.8.95Anderson Torres2020-05-21
|\ \ \ | | | | | | | | brave: 1.7.92 -> 1.8.95
| * | | brave: 1.7.92 -> 1.8.95Christian Mainka2020-05-08
| | | |
* | | | chromium: 81.0.4044.138 -> 83.0.4103.61Michael Weiss2020-05-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://chromereleases.googleblog.com/2020/05/stable-channel-update-for-desktop_19.html This update includes 38 security fixes. CVEs: CVE-2020-6465 CVE-2020-6466 CVE-2020-6467 CVE-2020-6468 CVE-2020-6469 CVE-2020-6470 CVE-2020-6471 CVE-2020-6472 CVE-2020-6473 CVE-2020-6474 CVE-2020-6475 CVE-2020-6476 CVE-2020-6477 CVE-2020-6478 CVE-2020-6479 CVE-2020-6480 CVE-2020-6481 CVE-2020-6482 CVE-2020-6483 CVE-2020-6484 CVE-2020-6485 CVE-2020-6486 CVE-2020-6487 CVE-2020-6488 CVE-2020-6489 CVE-2020-6490 CVE-2020-6491
* | | | vivaldi: 2.11 -> 3.0DonHugo692020-05-19
| | | |
* | | | firefox-devedition-bin: 77.0b6 -> 77.0b7adisbladis2020-05-19
| | | |
* | | | firefox-beta-bin: 77.0b6 -> 77.0b7adisbladis2020-05-19
| |_|/ |/| |
* | | firefox-devedition-bin: 76.0b8 -> 77.0b6adisbladis2020-05-16
| | |
* | | firefox-beta-bin: 76.0b8 -> 77.0b6adisbladis2020-05-16
| | |
* | | Merge pull request #87811 from andir/firefoxAndreas Rammhold2020-05-15
|\ \ \ | | | | | | | | firefox: 76.0 -> 76.0.1
| * | | firefox: 76.0 -> 76.0.1Andreas Rammhold2020-05-14
| | | |
* | | | Merge pull request #87733 from taku0/flashplayer-32.0.0.371Mario Rodas2020-05-14
|\ \ \ \ | |/ / / |/| | | flashplayer: 32.0.0.363 -> 32.0.0.371
| * | | flashplayer: 32.0.0.363 -> 32.0.0.371taku02020-05-12
| | | |
* | | | firefox: Add patch to fix AES GCM IV bit sizeaszlig2020-05-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Regression introduced by bce5268a216924820a486d09bc3aec7e8d6b8fa7. The bit size of the initialisation vector for AES GCM has been introduced in NSS version 3.52 in the CK_GCM_PARMS struct via the ulIvBits field. Unfortunately, Firefox 68.8.0 and 76.0 do not set this field and thus it gets initialised to zero, which in turn causes IV generation to fail. I found out about this because WebRTC stopped working after updating to NSS 3.52 and so I started bisecting. Since there wasn't an obvious error in Firefox hinting towards NSS but instead just the video stream ended up as a "null" stream, I didn't suspect the NSS update to be the culprit at first. So I verified a few times and then also started bisecting the actual commit in NSS that caused the issue. This turned out to be the problematic change: https://phabricator.services.mozilla.com/D63241 > One notable change was caused by an inconsistancy between the spec and > the released headers in PKCS#11 v2.40. CK_GCM_PARAMS had an extra > field in the header that was not in the spec. OASIS considers the > header file to be normative, so PKCS#11 v3.0 resolved the issue in > favor of the header file definition. Since the test I've used[1] was a bit flaky, I still didn't believe the result of the bisect to be accurate, but after running the test several times leading same results I dug through the above change line by line to get more clues. It fortunately didn't take that long to stumble upon the ulIvBits change (which is actually documented in the NSS 3.52 release notes[4], but I managed to blatantly ignore it for some reason) and started checking the Firefox source tree for changes regarding that field. Initialisation of that new field has been introduced[2] in preparation for the 76 release, but subsequently got reverted[3] prior to the release, because Firefox 76 is expected to be shipped with NSS 3.51, which didn't have the ulIvBits field. The patch I'm adding here is just a reintroduction of that change, because we're using NSS 3.52. Not initialising that field will break WebRTC and WebCrypto, which I think the former seems to gain in popularity these days ;-) Tested the change against the mentioned VM test[1] and also by testing manually using Jitsi Meet and Nextcloud Talk. [1]: https://github.com/aszlig/avonc/tree/884315838b6f0ebb32b/tests/talk [2]: https://hg.mozilla.org/mozilla-central/rev/3ed30e6b6de1 [3]: https://hg.mozilla.org/mozilla-central/rev/665137da70ee [4]: https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.52_release_notes Signed-off-by: aszlig <aszlig@nix.build>
* | | | qutebrowser: 1.11.0 -> 1.11.1Robert Schütz2020-05-12
|/ / / | | | | | | | | | fixes CVE-2020-11054
* / / github username: kjuvi -> xiorcalexiorcale2020-05-09
|/ /
* | treewide: per RFC45, remove more unquoted URLsPavol Rusnak2020-05-08
| |
* | Merge #86788: firefox 75.0 -> 76.0 (critical security)Vladimír Čunát2020-05-07
|\ \ | | | | | | | | | | | | https://www.mozilla.org/en-US/firefox/76.0/releasenotes/ Some of the changes were in master already, but whatever...
| * | firefox-devedition-bin: 76.0b4 -> 76.0b8Andreas Rammhold2020-05-04
| | |
| * | firefox-esr-68: 68.7.0esr -> 68.8.0esrAndreas Rammhold2020-05-04
| | |
| * | firefox-beta-bin: 76.0b4 -> 76.0b8Andreas Rammhold2020-05-04
| | |
| * | firefox-bin: 75.0 -> 76.0Andreas Rammhold2020-05-04
| | |
| * | firefox: 75.0 -> 76.0Andreas Rammhold2020-05-04
| |/
* | Merge pull request #81997 from eadwu/vivaldi-snapshot/fix-rpath-libdrm_gbmTim Steinbach2020-05-07
|\ \ | | | | | | vivaldi: include libdrm and libgbm
| * | vivaldi: include libdrm and libgbmEdmund Wu2020-03-07
| | |
* | | Merge pull request #87021 from primeos/chromiumMichael Weiss2020-05-06
|\ \ \ | | | | | | | | chromium: 81.0.4044.129 -> 81.0.4044.138
| * | | chromium: 81.0.4044.129 -> 81.0.4044.138Michael Weiss2020-05-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://chromereleases.googleblog.com/2020/05/stable-channel-update-for-desktop.html This update includes 3 security fixes. CVEs: CVE-2020-6831 CVE-2020-6464
* | | | firefox-bin: 75.0 -> 76.0Andreas Rammhold2020-05-06
| | | | | | | | | | | | | | | | Discussion: https://github.com/NixOS/nixpkgs/pull/86788
* | | | firefox-esr-68: 68.7.0esr -> 68.8.0esrAndreas Rammhold2020-05-06
|/ / / | | | | | | | | | Discussion: https://github.com/NixOS/nixpkgs/pull/86788
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-12 04:27:49 +0000