tor-browser

The Tor Browser
git clone https://git.dasho.dev/tor-browser.git
Log | Files | Refs | README | LICENSE

commit 7ef0fdc2f9e61d7bf99d66d1a32ad33b57f45454
parent d88df7a46fb0d36e937e227402b2d9b88163a79e
Author: Dan Baker <dbaker@mozilla.com>
Date:   Mon,  1 Dec 2025 21:04:12 -0700

Bug 2000941 - Vendor libwebrtc from 6edc2f3cf2

Upstream commit: https://webrtc.googlesource.com/src/+/6edc2f3cf2b05356851364259a006060236b4576
    Add reference to ReAuth guide

    Bug: chromium:415115279
    Change-Id: I117d38c67b504f0a1ea248c714792820321579ce
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/409460
    Commit-Queue: Andrew Mitchell <mitchella@google.com>
    Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org>
    Reviewed-by: Alexander Cooper <alcooper@chromium.org>
    Reviewed-by: Artem Titov <titovartem@webrtc.org>
    Cr-Commit-Position: refs/heads/main@{#45660}

Diffstat:
Mthird_party/libwebrtc/README.mozilla.last-vendor | 4++--
Mthird_party/libwebrtc/g3doc/become_a_committer.md | 2+-
2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/third_party/libwebrtc/README.mozilla.last-vendor b/third_party/libwebrtc/README.mozilla.last-vendor @@ -1,4 +1,4 @@ # ./mach python dom/media/webrtc/third_party_build/vendor-libwebrtc.py --from-local /Users/danielbaker/elm/.moz-fast-forward/moz-libwebrtc --commit mozpatches libwebrtc -libwebrtc updated from /Users/danielbaker/elm/.moz-fast-forward/moz-libwebrtc commit mozpatches on 2025-12-02T04:01:43.049914+00:00. +libwebrtc updated from /Users/danielbaker/elm/.moz-fast-forward/moz-libwebrtc commit mozpatches on 2025-12-02T04:03:58.204219+00:00. # base of lastest vendoring -fdb1f408c1 +6edc2f3cf2 diff --git a/third_party/libwebrtc/g3doc/become_a_committer.md b/third_party/libwebrtc/g3doc/become_a_committer.md @@ -75,7 +75,7 @@ recommended to apply for WebRTC committer rights obtaining process. 6. Also as any contributor you must sign and return the [Contributor License Agreement][4] -Two-factor authentication with a security key is a requirement for adding your account as a committer. If you haven't done so already, you'll need to set up a security key on your account. +Two-factor authentication with a security key is a requirement for adding your account as a committer. If you haven't done so already, you'll need to set up a security key on your account. For more information about this requirement see [Gerrit ReAuth](https://chromium.googlesource.com/chromium/src/+/main/docs/gerrit_reauth.md). ## WebRTC Committers expiration