tor-browser

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

commit b00273fcc1403feda9ea37c9f4b9515d613e6a8e
parent fb6405ce1de47b7b2dbdca22ca2d9480f7f42490
Author: Michael Froman <mfroman@mozilla.com>
Date:   Thu,  9 Oct 2025 14:42:16 -0500

Bug 1993083 - Vendor libwebrtc from 73e7a272d4

Upstream commit: https://webrtc.googlesource.com/src/+/73e7a272d4cc3f080aa9043ed3f2dc5e065c5772
    Update committers policy for 2FA requirement

    Bug: webrtc:415190329
    Change-Id: I0675ce63024ecf5adb998f8d481ba60d3fae6381
    Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/399860
    Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org>
    Reviewed-by: Harald Alvestrand <hta@webrtc.org>
    Commit-Queue: Andrew Mitchell <mitchella@google.com>
    Cr-Commit-Position: refs/heads/main@{#45154}

Diffstat:
Mthird_party/libwebrtc/README.mozilla.last-vendor | 4++--
Mthird_party/libwebrtc/g3doc/become_a_committer.md | 4+++-
2 files changed, 5 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 /home/mfroman/mozilla/elm/.moz-fast-forward/moz-libwebrtc --commit mozpatches libwebrtc -libwebrtc updated from /home/mfroman/mozilla/elm/.moz-fast-forward/moz-libwebrtc commit mozpatches on 2025-10-09T19:41:01.858240+00:00. +libwebrtc updated from /home/mfroman/mozilla/elm/.moz-fast-forward/moz-libwebrtc commit mozpatches on 2025-10-09T19:42:07.211080+00:00. # base of lastest vendoring -096fca9160 +73e7a272d4 diff --git a/third_party/libwebrtc/g3doc/become_a_committer.md b/third_party/libwebrtc/g3doc/become_a_committer.md @@ -75,12 +75,14 @@ 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. + ## WebRTC Committers expiration If a WebRTC committer isn't active on Gerrit (e.g. by uploading a CL, or participating in code reviews) for more than 1 year, they will lose their status as a WebRTC Committer and removed from the list of committers. An email will be -sent one week before the expiration date, giving the committer 7 days to +sent one week before the expiration date, giving the committer 7 days to demonstrate activity and maintain their WebRTC Committer status. [1]: https://webrtc.googlesource.com/src/+/refs/heads/main/docs/faq.md#to-be-a-contributor_do-i-need-to-sign-any-agreements