The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-09-19T09:32:05Zhttps://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40090Add links to all specs available on collector page2023-09-19T09:32:05ZGeorg KoppenAdd links to all specs available on collector pageWhile trying to review collector#40016 I was hunting down references for all the specs involved. It turns out they are all over the place and it's hard to keep track of them. On collector.html we link to some of those specs, which is goo...While trying to review collector#40016 I was hunting down references for all the specs involved. It turns out they are all over the place and it's hard to keep track of them. On collector.html we link to some of those specs, which is good. However, we should collect the links to all the missing specs and add them there, too, so we have at least one canonical place where all specs are just one click away.
Oh, and while we are at it we should replace those old gitweb links.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/core/tor/-/issues/40487On Android, LOCALSTATEDIR should be set to static path2023-09-18T22:24:40ZeighthaveOn Android, LOCALSTATEDIR should be set to static pathOn Android, there is no such thing as installing into the absolute system paths. So we have to hack around that assumption in `./configure`. That means that `LOCALSTATEDIR` ends up getting set to build paths, breaking reproducibility. ...On Android, there is no such thing as installing into the absolute system paths. So we have to hack around that assumption in `./configure`. That means that `LOCALSTATEDIR` ends up getting set to build paths, breaking reproducibility. Since having a compiled-in `LOCALSTATEDIR` is worthless on Android, it should not be used for Android build. It could just be hard-coded to some debug path like `/data/local/tmp`.
This is similar to !460
@n8fr8 FYIAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/network-health/metrics/descriptorParser/-/issues/39Make sure data parsing in the parser and sent to VictoriaMetrics is correct2023-09-18T14:35:11ZHiroMake sure data parsing in the parser and sent to VictoriaMetrics is correctWe should verify that the measurements we see in victoria metrics are correct given all the development that we have been doing on descriptorParser.We should verify that the measurements we see in victoria metrics are correct given all the development that we have been doing on descriptorParser.HiroHirohttps://gitlab.torproject.org/tpo/network-health/metrics/networkstatusapi/-/issues/6Deploy network status api2023-09-18T14:30:34ZHiroDeploy network status apiThis issue marks deployment activities for the NetworkStatusApi at metrics-api.tpoThis issue marks deployment activities for the NetworkStatusApi at metrics-api.tpoHiroHirohttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40693upgrade alberti to bullseye ... er bookworm!2023-09-14T18:32:28Zanarcatupgrade alberti to bullseye ... er bookworm!alberti could be a tricky part, so it's not part of the large bullseye upgrade batches (#40690 or #40692).
just do the upgrade and see what happens, i guess, although while we're here, we might want to consider switching to bcrypt or ye...alberti could be a tricky part, so it's not part of the large bullseye upgrade batches (#40690 or #40692).
just do the upgrade and see what happens, i guess, although while we're here, we might want to consider switching to bcrypt or yescrypt for the mail password hashing (https://gitlab.torproject.org/tpo/tpa/team/-/issues/40492).Debian 11 bullseye upgradeanarcatanarcat2023-09-13https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40952Prepare Tor Browser Stable 12.5.42023-09-14T17:19:27ZPier Angelo VendramePrepare Tor Browser Stable 12.5.4<details>
<summary>Explanation of variables</summary>
- `$(BUILD_SERVER)` : the server the main builder is using to build a tor-browser release
- `$(BUILDER)` : whomever is building the release on the $(BUILD_SERVER)
- **example** :...<details>
<summary>Explanation of variables</summary>
- `$(BUILD_SERVER)` : the server the main builder is using to build a tor-browser release
- `$(BUILDER)` : whomever is building the release on the $(BUILD_SERVER)
- **example** : `pierov`
- `$(STAGING_SERVER)` : the server the signer is using to to run the signing process
- `$(ESR_VERSION)` : the Mozilla defined ESR version, used in various places for building tor-browser tags, labels, etc
- **example** : `91.6.0`
- `$(TOR_BROWSER_MAJOR)` : the Tor Browser major version
- **example** : `11`
- `$(TOR_BROWSER_MINOR)` : the Tor Browser minor version
- **example** : either `0` or `5`; Alpha's is always `(Stable + 5) % 10`
- `$(TOR_BROWSER_VERSION)` : the Tor Browser version in the format
- **example** : `12.5a3`, `12.0.3`
- `$(BUILD_N)` : a project's build revision within a its branch; this is separate from the `$(TOR_BROWSER_BUILD_N)` value; many of the Firefox-related projects have a `$(BUILD_N)` suffix and may differ between projects even when they contribute to the same build.
- **example** : `build1`
- `$(TOR_BROWSER_BUILD_N)` : the tor-browser build revision for a given Tor Browser release; used in tagging git commits
- **example** : `build2`
- **NOTE** : A project's `$(BUILD_N)` and `$(TOR_BROWSER_BUILD_N)` may be the same, but it is possible for them to diverge. For example :
- if we have multiple Tor Browser releases on a given ESR branch the two will become out of sync as the `$(BUILD_N)` value will increase, while the `$(TOR_BROWSER_BUILD_N)` value may stay at `build1` (but the `$(TOR_BROWSER_VERSION)` will increase)
- if we have build failures unrelated to `tor-browser`, the `$(TOR_BROWSER_BUILD_N)` value will increase while the `$(BUILD_N)` will stay the same.
- `$(TOR_BROWSER_VERSION)` : the published Tor Browser version
- **example** : `11.5a6`, `11.0.7`
- `$(TBB_BUILD_TAG)` : the `tor-browser-build` build tag used to build a given Tor Browser version
- **example** : `tbb-12.0.7-build1`
</details>
**NOTE** It is assumed that the `tor-browser` stable rebase and security backport tasks have been completed
<details>
<summary>Building</summary>
### tor-browser-build: https://gitlab.torproject.org/tpo/applications/tor-browser-build.git
Tor Browser Stable lives in the various `maint-$(TOR_BROWSER_MAJOR).$(TOR_BROWSER_MINOR)` (and possibly more specific) branches
- [x] Update `rbm.conf`
- [x] `var/torbrowser_version` : update to next version
- [ ] `var/torbrowser_build` : update to `$(TOR_BROWSER_BUILD_N)`
- [x] ***(Desktop Only)***`var/torbrowser_incremental_from` : update to previous Desktop version
- **IMPORTANT**: Really *actually* make sure this is the previous Desktop version or else the `make torbrowser-incrementals-*` step will fail
- [x] Update Desktop-specific build configs
- [x] Update `projects/firefox/config`
- [x] `browser_build` : update to match `tor-browser` tag
- [x] ***(Optional)*** `var/firefox_platform_version` : update to latest `$(ESR_VERSION)` if rebased
- [x] Update `projects/translation/config`:
- [x] run `make list_translation_updates-release` to get updated hashes
- [x] `steps/base-browser/git_hash` : update with `HEAD` commit of project's `base-browser` branch
- [ ] `steps/base-browser-fluent/git_hash` : update with `HEAD` commit of project's `basebrowser-newidentityftl` branch
- [x] `steps/tor-browser/git_hash` : update with `HEAD` commit of project's `tor-browser` branch
- [x] `steps/fenix/git_hash` : update with `HEAD` commit of project's `fenix-torbrowserstringsxml` branch
- [x] Update Android-specific build configs
- [x] Update `projects/geckoview/config`
- [x] `browser_build` : update to match `tor-browser` tag
- [x] ***(Optional)*** `var/geckoview_version` : update to latest `$(ESR_VERSION)` if rebased
- [ ] ***(Optional)*** Update `projects/tor-android-service/config`
- [ ] `git_hash` : update with `HEAD` commit of project's `main` branch
- [ ] ***(Optional)*** Update `projects/application-services/config`:
**NOTE** we don't currently have any of our own patches for this project
- [ ] `git_hash` : update to appropriate git commit associated with `$(ESR_VERSION)`
- [ ] ***(Optional)*** Update `projects/android-components/config`:
- [ ] `android_components_build` : update to match stable android-components tag
- [ ] ***(Optional)*** Update `projects/fenix/config`
- [ ] `fenix_build` : update to match fenix tag
- [x] Update allowed_addons.json by running (from `tor-browser-build` root):
- `./tools/fetch_allowed_addons.py > projects/browser/allowed_addons.json`
- [x] Update common build configs
- [x] Check for NoScript updates here : https://addons.mozilla.org/en-US/firefox/addon/noscript
- [ ] ***(Optional)*** If new version available, update `noscript` section of `input_files` in `projects/browser/config`
- [ ] `URL`
- [ ] `sha256sum`
- [x] Check for OpenSSL updates here : https://www.openssl.org/source/
- [x] ***(Optional)*** If new 1.X.Y version available, update `projects/openssl/config`
- [x] `version` : update to next 1.X.Y version
- [x] `input_files/sha256sum` : update to sha256 sum of source tarball
- [ ] Check for zlib updates here: https://github.com/madler/zlib/releases
- [ ] **(Optional)** If new tag available, update `projects/zlib/config`
- [ ] `version` : update to next release tag
- [x] Check for tor updates here : https://gitlab.torproject.org/tpo/core/tor/-/tags
- [ ] ***(Optional)*** Update `projects/tor/config`
- [ ] `version` : update to latest non `-alpha` tag (ping dgoulet or ahf if unsure)
- [x] Check for go updates here : https://golang.org/dl
- **NOTE** : Tor Browser Stable uses the latest of the *previous* Stable major series go version (apart from the transition phase from Tor Browser Alpha to Stable, in which case Tor Browser Stable may use the latest major series go version)
- [x] ***(Optional)*** Update `projects/go/config`
- [x] `version` : update go version
- [x] `input_files/sha256sum` for `go` : update sha256sum of archive (sha256 sums are displayed on the go download page)
- [x] Check for manual updates by running (from `tor-browser-build` root): `./tools/fetch-manual.py`
- [x] ***(Optional)*** If new version is available:
- [x] Upload the downloaded `manual_$PIPELINEID.zip` file to people.tpo
- [x] Update `projects/manual/config`:
- [x] Change the `version` to `$PIPELINEID`
- [x] Update `sha256sum` in the `input_files` section
- [x] ***(Optional)*** Update the URL if you have uploaded to a different people.tpo home
- [x] Update `ChangeLog.txt`
- [x] Ensure ChangeLog.txt is sync'd between alpha and stable branches
- [x] Check the linked issues: ask people to check if any are missing, remove the not fixed ones
- [x] Run `tools/fetch-changelogs.py $(TOR_BROWSER_VERSION)` or `tools/fetch-changelogs.py '#$(ISSUE_NUMBER)'`
- Make sure you have `requests` installed (e.g., `apt install python3-requests`)
- The first time you run this script you will need to generate an access token; the script will guide you
- [x] Copy the output of the script to the beginning of `ChangeLog.txt` and adjust its output
- **NOTE** : If you used the issue number, you will need to write the Tor Browser version manually
- [x] ***(Optional)*** Under `All Platforms` include any version updates for:
- [x] Translations
- [x] OpenSSL
- [ ] NoScript
- [ ] zlib
- [ ] tor daemon
- [x] ***(Optional)*** Under `Windows + macOS + Linux` include updates for:
- [x] Firefox
- [x] ***(Optional)*** Under `Android`, include updates for:
- [x] Geckoview
- [x] ***(Optional)*** Under `Build System/All Platforms` include updates for:
- [x] Go
- [x] Open MR with above changes
- [x] Merge
- [x] Sign/Tag commit: `make torbrowser-signtag-release`
- [x] Push tag to `origin`
- [x] Begin build on `$(BUILD_SERVER)` (fix any issues in subsequent MRs)
- [ ] **TODO** Submit build-tag to Mullvad build infra
- [x] Ensure builders have matching builds
</details>
<details>
<summary>Communications</summary>
### notify stakeholders
<details>
<summary>email template</summary>
Subject:
Tor Browser $(TOR_BROWSER_VERION) (Android, Windows, macOS, Linux)
Body:
Hello All,
Unsigned Tor Browser $(TOR_BROWSER_VERSION) release candidate builds are now available for testing:
- https://tb-build-05.torproject.org/~$(BUILDER)/builds/release/unsigned/$(TOR_BROWSER_VERSION)/
The full changelog can be found here:
- https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/blob/$(TBB_BUILD_TAG)/ChangeLog.txt
</details>
- [x] Email tor-qa mailing list: tor-qa@lists.torproject.org
- ***(Optional)*** Additional information:
- [ ] Note any new functionality which needs testing
- [ ] Link to any known issues
- [x] Email packagers:
- Recipients:
- Tails dev mailing list: tails-dev@boum.org
- Guardian Project: nathan@guardianproject.info
- torbrowser-launcher: micah@micahflee.com
- FreeBSD port: freebsd@sysctl.cz <!-- Gitlab user maxfx -->
- OpenBSD port: caspar@schutijser.com <!-- Gitlab user cschutijser -->
- [ ] ***(Optional)*** Note any changes which may affect packaging/downstream integration
</details>
<details>
<summary>Signing</summary>
### signing
- **NOTE** : In practice, it's most efficient to have the blog post and website updates ready to merge, since signing doesn't take very long
- [x] On `$(STAGING_SERVER)`, ensure updated:
- [x] `tor-browser-build` is on the right commit: `git tag -v tbb-$(TOR_BROWSER_VERSION)-$(TOR_BROWSER_BUILD_N) && git checkout tbb-$(TOR_BROWSER_VERSION)-$(TOR_BROWSER_BUILD_N)`
- [x] `tor-browser-build/tools/signing/set-config.hosts`
- `ssh_host_builder` : ssh hostname of machine with unsigned builds
- **NOTE** : `tor-browser-build` is expected to be in the `$HOME` directory)
- `ssh_host_linux_signer` : ssh hostname of linux signing machine
- `ssh_host_macos_signer` : ssh hostname of macOS signing machine
- [x] `tor-browser-build/tools/signing/set-config.macos-notarization`
- `macos_notarization_user` : the email login for a tor notariser Apple Developer account
- [x] `set-config.update-responses`
- `update_responses_repository_dir` : directory where you cloned `git@gitlab.torproject.org:tpo/applications/tor-browser-update-responses.git`
- [x] `tor-browser-build/tools/signing/set-config.tbb-version`
- `tbb_version` : tor browser version string, same as `var/torbrowser_version` in `rbm.conf` (examples: `11.5a12`, `11.0.13`)
- `tbb_version_build` : the tor-browser-build build number (if `var/torbrowser_build` in `rbm.conf` is `buildN` then this value is `N`)
- `tbb_version_type` : either `alpha` for alpha releases or `release` for stable releases
- [x] On `$(STAGING_SERVER)` in a separate `screen` session, run the macOS proxy script:
- `cd tor-browser-build/tools/signing/`
- `./macos-signer-proxy`
- [x] On `$(STAGING_SERVER)` in a separate `screen` session, ensure tor daemon is running with SOCKS5 proxy on the default port 9050
- [x] run do-all-signing script:
- `cd tor-browser-build/tools/signing/`
- `./do-all-signing.torbrowser`
- **NOTE**: at this point the signed binaries should have been copied to `staticiforme`
- [x] Update `staticiforme.torproject.org`:
- From `screen` session on `staticiforme.torproject.org`:
- [x] Static update components : `static-update-component cdn.torproject.org && static-update-component dist.torproject.org`
- [x] Enable update responses : `sudo -u tb-release ./deploy_update_responses-release.sh`
- [x] Remove old release data from following places:
- **NOTE** : Skip this step if we need to hold on to older versions for some reason (for example, this is an Andoid or Desktop-only release, or if we need to hold back installers in favor of build-to-build updates if there are signing issues, etc)
- [x] `/srv/cdn-master.torproject.org/htdocs/aus1/torbrowser`
- [x] `/srv/dist-master.torproject.org/htdocs/torbrowser`
- [x] Static update components (again) : `static-update-component cdn.torproject.org && static-update-component dist.torproject.org`
- [x] Publish APKs to Google Play:
- Log into https://play.google.com/apps/publish
- Select `Tor Browser` app
- Navigate to `Release > Production` and click `Create new release` button:
- Upload the `*.multi.apk` APKs
- Update Release Name to Tor Browser version number
- Update Release Notes
- Next to 'Release notes', click `Copy from a previous release`
- Edit blog post url to point to most recent blog post
- Save, review, and configure rollout percentage
- [ ] 25% rollout when publishing a scheduled update
- [x] 100% rollout when publishing a security-driven release
- [ ] Update rollout percentage to 100% after confirmed no major issues
</details>
<details>
<summary>Signature verification</summary>
<details>
<summary>Check whether the .exe files got properly signed and timestamped</summary>
```
# Point OSSLSIGNCODE to your osslsigncode binary
pushd tor-browser-build/${channel}/signed/$TORBROWSER_VERSION
OSSLSIGNCODE=/path/to/osslsigncode
../../../tools/authenticode_check.sh
popd
```
</details>
<details>
<summary>Check whether the MAR files got properly signed</summary>
```
# Point NSSDB to your nssdb containing the mar signing certificate
# Point SIGNMAR to your signmar binary
# Point LD_LIBRARY_PATH to your mar-tools directory
pushd tor-browser-build/${channel}/signed/$TORBROWSER_VERSION
NSSDB=/path/to/nssdb
SIGNMAR=/path/to/mar-tools/signmar
LD_LIBRARY_PATH=/path/to/mar-tools/
../../../tools/marsigning_check.sh
popd
```
</details>
</details>
<details>
<summary>Publishing</summary>
### website: https://gitlab.torproject.org/tpo/web/tpo.git
- [x] `databags/versions.ini` : Update the downloads versions
- `torbrowser-stable/version` : sort of a catch-all for latest stable version
- `torbrowser-alpha/version` : sort of a catch-all for latest stable version
- `torbrowser-*-stable/version` : platform-specific stable versions
- `torbrowser-*-alpha/version` : platform-specific alpha versions
- `tor-stable`,`tor-alpha` : set by tor devs, do not touch
- [x] Push to origin as new branch, open 'Draft :' MR
- [x] Remove `Draft:` from MR once signed-packages are uploaded
- [x] Merge
- [x] Publish after CI passes and builds are published
### blog: https://gitlab.torproject.org/tpo/web/blog.git
- [x] Duplicate previous Stable or Alpha release blog post as appropriate to new directory under `content/blog/new-release-tor-browser-$(TOR_BROWSER_VERSION)` and update with info on release :
- [x] Run `tools/signing/create-blog-post` which should create the new blog post from a template (edit set-config.blog to set you local blog directory)
- [ ] Update Tor Browser version numbers
- [ ] Note any ESR rebase
- [ ] Link to any Firefox security updates from ESR upgrade
- [ ] Link to any Android-specific security backports
- [ ] Note any updates to :
- tor
- OpenSSL
- NoScript
- [ ] Convert ChangeLog.txt to markdown format used here by :
- `tor-browser-build/tools/changelog-format-blog-post`
- [x] Push to origin as new branch, open `Draft:` MR
- [x] Remove `Draft:` from MR once signed-packages are uploaded
- [x] Merge
- [x] Publish after CI passes and website has been updated
### tor-announce mailing list
<details>
<summary>email template</summary>
Subject:
New Release: Tor Browser $(TOR_BROWSER_VERSION) (Android, Windows, macOS, Linux)
Body:
Hi everyone,
Tor Browser $(TOR_BROWSER_VERSION) has now been published for all platforms. For details please see our blog post:
- $(BLOG_POST_URL)
</details>
- [x] Email tor-announce mailing list: tor-announce@lists.torproject.org
- **(Optional)** Additional information:
- [ ] Link to any known issues
</details>richardrichardhttps://gitlab.torproject.org/tpo/network-health/metrics/onionoo/-/issues/40037Add transport to summary document and implement search filter2023-09-14T16:17:10ZHiroAdd transport to summary document and implement search filterNeeded for: https://gitlab.torproject.org/tpo/network-health/metrics/website/-/merge_requests/57Needed for: https://gitlab.torproject.org/tpo/network-health/metrics/website/-/merge_requests/57HiroHirohttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41320duplicate GID between tagtor and metrics-api2023-09-14T15:35:09Zanarcatduplicate GID between tagtor and metrics-apithe metrics-api and tagtor groups have the same GID, which raises this error in `ud-replicate`, even on unrelated servers:
```
root@cdn-backend-sunet-02:~# ud-replicate
receiving file list ... done
sent 19 bytes received 837 bytes 1,...the metrics-api and tagtor groups have the same GID, which raises this error in `ud-replicate`, even on unrelated servers:
```
root@cdn-backend-sunet-02:~# ud-replicate
receiving file list ... done
sent 19 bytes received 837 bytes 1,712.00 bytes/sec
total size is 226,362 speedup is 264.44
makedb:cdn-backend-sunet-02.torproject.org/group.tdb:69: duplicate key
```
That's because both groups have the same GID (`2196`):
```
571 gid=tagtor,ou=users,dc=torproject,dc=org
gid: tagtor
gidNumber: 2196
objectClass: top
objectClass: debianGroup
[...]
587 gid=metrics-api,ou=users,dc=torproject,dc=org
gid: metrics-api
gidNumber: 2196
objectClass: top
objectClass: debianGroup
```
it's the same for the metrics-api and tagtor users: they share the same UID.
there are two problems here:
1. duplicate UID/GIDs - in general that should be avoided, but this is particularly a problem because both users/groups pairs are deployed on the same server (`metricsdb-01`), it's a miracle any of this worked at all
2. this shouldn't error *everywhere* and I worry this is a sign that users are not syncing properly
This could be related to the botched LDAP upgrade I did yesterday (#40693), but I suspect the duplication has been there since August 25th. We haven't noticed then possibly because `makedb` was less strict or some other thing changed... unclear.
In any case, we need to split those UIDs. @hiro what should those UIDs be? what files should be owned by who?anarcatanarcathttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40953Prepare Mullvad Browser Stable 12.5.42023-09-14T15:31:48ZPier Angelo VendramePrepare Mullvad Browser Stable 12.5.4<details>
<summary>Explanation of variables</summary>
- `$(BUILD_SERVER)` : the server the main builder is using to build a mullvad-browser release
- `$(BUILDER)` : whomever is building the release on the $(BUILD_SERVER)
- **example...<details>
<summary>Explanation of variables</summary>
- `$(BUILD_SERVER)` : the server the main builder is using to build a mullvad-browser release
- `$(BUILDER)` : whomever is building the release on the $(BUILD_SERVER)
- **example** : `pierov`
- `$(STAGING_SERVER)` : the server the signer is using to to run the signing process
- `$(ESR_VERSION)` : the Mozilla defined ESR version, used in various places for building mullvad-browser tags, labels, etc
- **example** : `91.6.0`
- `$(MULLVAD_BROWSER_MAJOR)` : the Mullvad Browser major version
- **example** : `11`
- `$(MULLVAD_BROWSER_MINOR)` : the Mullvad Browser minor version
- **example** : either `0` or `5`; Alpha's is always `(Stable + 5) % 10`
- `$(MULLVAD_BROWSER_VERSION)` : the Mullvad Browser version in the format
- **example** : `12.5a3`, `12.0.3`
- `$(BUILD_N)` : a project's build revision within a its branch; this is separate from the `$(MULLVAD_BROWSER_BUILD_N)` value; many of the Firefox-related projects have a `$(BUILD_N)` suffix and may differ between projects even when they contribute to the same build.
- **example** : `build1`
- `$(MULLVAD_BROWSER_BUILD_N)` : the mullvad-browser build revision for a given Mullvad Browser release; used in tagging git commits
- **example** : `build2`
- **NOTE** : A project's `$(BUILD_N)` and `$(MULLVAD_BROWSER_BUILD_N)` may be the same, but it is possible for them to diverge. For **example** :
- if we have multiple Mullvad Browser releases on a given ESR branch the two will become out of sync as the `$(BUILD_N)` value will increase, while the `$(MULLVAD_BROWSER_BUILD_N)` value may stay at `build1` (but the `$(MULLVAD_BROWSER_VERSION)` will increase)
- if we have build failures unrelated to `mullvad-browser`, the `$(MULLVAD_BROWSER_BUILD_N)` value will increase while the `$(BUILD_N)` will stay the same.
- `$(MULLVAD_BROWSER_VERSION)` : the published Mullvad Browser version
- **example** : `11.5a6`, `11.0.7`
- `$(MB_BUILD_TAG)` : the `tor-browser-build` build tag used to build a given Mullvad Browser version
- **example** : `mb-12.0.7-build1`
</details>
**NOTE** It is assumed that the `tor-browser` stable rebase and security backport tasks have been completed
<details>
<summary>Building</summary>
### tor-browser-build: https://gitlab.torproject.org/tpo/applications/tor-browser-build.git
Mullvad Browser Stable lives in the various `maint-$(MULLVAD_BROWSER_MAJOR).$(MULLVAD_BROWSER_MINOR)` (and possibly more specific) branches
- [x] Update `rbm.conf`
- [x] `var/torbrowser_version` : update to next version
- [x] `var/torbrowser_build` : update to `$(MULLVAD_BROWSER_BUILD_N)`
- [x] `var/torbrowser_incremental_from` : update to previous Desktop version
- **IMPORTANT**: Really *actually* make sure this is the previous Desktop version or else the `make mullvadbrowser-incrementals-*` step will fail
- [x] Update build configs
- [x] Update `projects/firefox/config`
- [x] `browser_build` : update to match `mullvad-browser` tag
- [x] ***(Optional)*** `var/firefox_platform_version` : update to latest `$(ESR_VERSION)` if rebased
- [x] Update `projects/translation/config`:
- [x] run `make list_translation_updates-release` to get updated hashes
- [x] `steps/base-browser/git_hash` : update with `HEAD` commit of project's `base-browser` branch
- [x] `steps/base-browser-fluent/git_hash` : update with `HEAD` commit of project's `basebrowser-newidentityftl` branch
- [x] Update common build configs
- [x] Check for NoScript updates here : https://addons.mozilla.org/en-US/firefox/addon/noscript
- [ ] ***(Optional)*** If new version available, update `noscript` section of `input_files` in `projects/browser/config`
- [ ] `URL`
- [ ] `sha256sum`
- [x] Check for uBlock-origin updates here : https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/
- [ ] ***(Optional)*** If new version available, update `ublock-origin` section of `input_files` in `projects/browser/config`
- [ ] `URL`
- [ ] `sha256sum`
- [x] Check for Mullvad Privacy Companion updates here : https://github.com/mullvad/browser-extension/releases
- [ ] ***(Optional)*** If new version available, update `mullvad-extension` section of `input_files` in `projects/browser/config`
- [ ] `URL`
- [ ] `sha256sum`
- [x] Open MR with above changes
- [x] Merge
- [x] Sign/Tag commit: `make mullvadbrowser-signtag-release`
- [x] Push tag to `origin`
- [x] Begin build on `$(BUILD_SERVER)` (fix any issues in subsequent MRs)
- [ ] **TODO** Submit build-tag to Mullvad build infra
- [x] Ensure builders have matching builds
</details>
<details>
<summary>QA</summary>
### send the build
- [x] Email Mullvad QA: support@mullvad.net, rui@mullvad.net
<details>
<summary>email template</summary>
Subject:
New build: Mullvad Browser $(MULLVAD_BROWSER_VERION) (unsigned)
Body:
unsigned builds: https://tb-build-05.torproject.org/~$(BUILDER)/builds/mullvadbrowser/release/unsigned/$(MB_BUILD_TAG)
changelog:
...
</details>
- ***(Optional)*** Add additional information:
- [ ] Note any new functionality which needs testing
- [ ] Link to any known issues
</details>
<details>
<summary>Signing</summary>
### signing
- [x] On `$(STAGING_SERVER)`, ensure updated:
- [x] `tor-browser-build/tools/signing/set-config.hosts`
- `ssh_host_builder` : ssh hostname of machine with unsigned builds
- **NOTE** : `tor-browser-build` is expected to be in the `$HOME` directory)
- `ssh_host_linux_signer` : ssh hostname of linux signing machine
- `ssh_host_macos_signer` : ssh hostname of macOS signing machine
- [x] `tor-browser-build/tools/signing/set-config.macos-notarization`
- `macos_notarization_user` : the email login for a mullvad notariser Apple Developer account
- [x] `set-config.update-responses`
- `update_responses_repository_dir` : directory where you cloned `git@gitlab.torproject.org:tpo/applications/mullvad-browser-update-responses.git`
- [x] `tor-browser-build/tools/signing/set-config.tbb-version`
- `tbb_version` : mullvad browser version string, same as `var/torbrowser_version` in `rbm.conf` (examples: `11.5a12`, `11.0.13`)
- `tbb_version_build` : the tor-browser-build build number (if `var/torbrowser_build` in `rbm.conf` is `buildN` then this value is `N`)
- `tbb_version_type` : either `alpha` for alpha releases or `release` for stable releases
- [x] On `$(STAGING_SERVER)` in a separate `screen` session, run the macOS proxy script:
- `cd tor-browser-build/tools/signing/`
- `./macos-signer-proxy`
- [x] On `$(STAGING_SERVER)` in a separate `screen` session, ensure tor daemon is running with SOCKS5 proxy on the default port 9050
- [x] run do-all-signing script:
- `cd tor-browser-build/tools/signing/`
- `./do-all-signing.mullvadbrowser`
- **NOTE**: at this point the signed binaries should have been copied to `staticiforme`
- [x] Update `staticiforme.torproject.org`:
- From `screen` session on `staticiforme.torproject.org`:
- [x] Static update components : `static-update-component dist.torproject.org`
- [x] Remove old release data from `/srv/dist-master.torproject.org/htdocs/mullvadbrowser`
- [x] Static update components (again) : `static-update-component dist.torproject.org`
</details>
<details>
<summary>Publishing</summary>
### email
- [x] Email Mullvad with release information: support@mullvad.net, rui@mullvad.net
<details>
<summary>email template</summary>
Subject:
New build: Mullvad Browser $(MULLVAD_BROWSER_VERION) (signed)
Body:
signed builds: https://dist.torproject.org/mullvadbrowser/$(MULLVAD_BROWSER_VERSION)
update_response hashes: $(MULLVAD_UPDATE_RESPONSES_HASH)
changelog:
...
</details>
### mullvad-browser (github): https://github.com/mullvad/mullvad-browser/
- [x] Push this release's associated `mullvad-browser.git` branch to github
- [x] Push this release's associated tags to github:
- [x] Firefox ESR tag
- **example** : `FIREFOX_102_12_0esr_BUILD1,`
- [x] `base-browser` tag
- **example** : `base-browser-102.12.0esr-12.0-1-build1`
- [x] `mullvad-browser` tag
- **example** : `mullvad-browser-102.12.0esr-12.0-1-build1`
- [x] Sign+Tag additionally the `mullvad-browser.git` `firefox` commit used in build:
- **Tag**: `$(MULLVAD_BROWSER_VERSION)`
- **example** : `12.0.7`
- **Message**: `$(ESR_VERSION)esr-based $(MULLVAD_BROWSER_VERSION)`
- **example** : `102.12.0esr-based 12.0.7`
- [x] Push tag to github
</details>
<details>
<summary>Downstream</summary>
### notify packagers
- [x] **(Once Mullvad Updates their Github Releases Page)** Email downstream consumers:
<details>
<summary>email template</summary>
...
...
</details>
- [x] flathub package maintainer: proletarius101@protonmail.com
- [x] arch package maintainer: bootctl@gmail.com
- [x] nixOS package maintainer: dev@felschr.com
### merge requests
- [x] homebrew: https://github.com/Homebrew/homebrew-cask/blob/master/Casks/mullvad-browser.rb
- **NOTE**: should just need to update the version to latest
</details>richardrichardhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41119brainstorm ideas for TPA in-person meeting2023-09-14T14:03:42Zanarcatbrainstorm ideas for TPA in-person meetingwe'll have the chance to meet in person with a bunch of people, we should use it. we'll share "THE BAR" space with the ops team, but we can welcome other folks in our session as well.
Once settled, we should throw the results in https:/...we'll have the chance to meet in person with a bunch of people, we should use it. we'll share "THE BAR" space with the ops team, but we can welcome other folks in our session as well.
Once settled, we should throw the results in https://nc.torproject.net/f/458264 (or the wiki? see also https://gitlab.torproject.org/tpo/team/-/wikis//2023-Tor-Meeting-Costa-Rica-Wiki#schedule)
I suggest we proceed by making one comment here per idea, and :+1: the ones we like, asynchronously.
/cc @gaba @lavamind @kezanarcatanarcat2023-04-14https://gitlab.torproject.org/tpo/tpa/team/-/issues/41319Install python3-requests apt package on tb-build-02 and -032023-09-13T17:26:18ZrichardInstall python3-requests apt package on tb-build-02 and -03Please and thank you (not urgent) :)
- https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_requests/810#note_2942392Please and thank you (not urgent) :)
- https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_requests/810#note_2942392Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40763automate BTCpayserver upgrades2023-09-13T17:23:26Zanarcatautomate BTCpayserver upgradesin #33750 we switched the BTCpayserver to be hosted in TPA infra, which solves a lot of problems: user accounts, backups, monitoring, etc is covered by our normal policies.
but the app itself isn't upgraded automatically. figure out how...in #33750 we switched the BTCpayserver to be hosted in TPA infra, which solves a lot of problems: user accounts, backups, monitoring, etc is covered by our normal policies.
but the app itself isn't upgraded automatically. figure out how we'll take care of that, either through a docker-compose cron job, or manually.anarcatanarcat2023-10-13https://gitlab.torproject.org/tpo/network-health/tor-weather/-/issues/64Dependency Dashboard2023-09-13T08:25:52ZRenovate BotDependency DashboardThis issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Open
These updates have all been created already. Click a checkbo...This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
- [x] <!-- rebase-branch=renovate/bandit-1.x-lockfile -->[chore(deps): update dependency bandit to v1.7.5](!74)
- [x] <!-- rebase-branch=renovate/black-23.x-lockfile -->[chore(deps): update dependency black to v23](!85)
## Detected dependencies
<details><summary>gitlabci</summary>
<blockquote>
<details><summary>.gitlab-ci.yml</summary>
</details>
</blockquote>
</details>
<details><summary>poetry</summary>
<blockquote>
<details><summary>pyproject.toml</summary>
- `python-dotenv *`
- `requests *`
- `psycopg2-binary *`
- `flask-assets *`
- `glob2 *`
- `pyscss *`
- `pyjwt *`
- `bcrypt *`
- `cryptography *`
- `flask *`
- `flask-restx *`
- `werkzeug *`
- `flask-sqlalchemy *`
- `flask-login *`
- `black *`
- `flake8 *`
- `mypy *`
- `pytest *`
- `pytest-cov *`
- `isort *`
- `bandit *`
- `djlint *`
</details>
</blockquote>
</details>Renovate BotRenovate Bothttps://gitlab.torproject.org/tpo/network-health/tor-weather/-/issues/74Dependency Dashboard2023-09-13T08:25:07ZRenovate BotDependency DashboardThis issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Open
These updates have all been created already. Click a checkbo...This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
- [x] <!-- rebase-branch=renovate/djlint-1.x-lockfile -->[chore(deps): update dependency djlint to v1.32.1](!103)
## Detected dependencies
<details><summary>gitlabci</summary>
<blockquote>
<details><summary>.gitlab-ci.yml</summary>
</details>
</blockquote>
</details>
<details><summary>poetry</summary>
<blockquote>
<details><summary>pyproject.toml</summary>
- `python-dotenv *`
- `requests *`
- `psycopg2-binary *`
- `flask-assets *`
- `glob2 *`
- `pyscss *`
- `pyjwt *`
- `bcrypt *`
- `cryptography *`
- `flask *`
- `flask-restx *`
- `werkzeug *`
- `flask-sqlalchemy *`
- `flask-login *`
- `flask-migrate ^4.0.4`
- `black *`
- `flake8 *`
- `mypy *`
- `pytest *`
- `pytest-cov *`
- `isort *`
- `bandit *`
- `djlint *`
</details>
</blockquote>
</details>Renovate BotRenovate Bothttps://gitlab.torproject.org/tpo/core/tor/-/issues/40848tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_una...2023-09-12T14:42:45Ztlator_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)### Summary
[warn] tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)
This happens at least on iOS and macOS.
I have also s...### Summary
[warn] tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)
This happens at least on iOS and macOS.
I have also seen this in older versions. Not just me, users report it, too:
https://github.com/guardianproject/orbot-apple/issues/76
### Steps to reproduce:
1. git clone https://github.com/iCepa/Tor.framework
2. cd Tor.framework
3. pod install
4. open Example/Tor.xcworkspace
5. run Tor-Example or Tor-Example-Mac
### What is the current bug behavior?
Everything keeps working, but debug log shows this:
```
Aug 30 12:08:01.023 [notice] Tor 0.4.8.4 (git-6d6bd21b9d364302) running on Darwin with Libevent 2.1.12-stable, OpenSSL 3.1.2, Zlib 1.2.11, Liblzma 5.4.4, Libzstd N/A and Unknown N/A as libc.
Aug 30 12:08:01.023 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Aug 30 12:08:01.023 [notice] Configuration file "/Users/berhart/Library/Developer/CoreSimulator/Devices/D3204428-26B1-4C55-8177-B3057F6F67AC/data/Containers/Data/Application/C659E399-A46C-4058-8F8E-86E3EFA82568/.torrc" not present, using reasonable defaults.
Aug 30 12:08:01.025 [notice] Opening Socks listener on 127.0.0.1:9050
Aug 30 12:08:01.025 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Aug 30 12:08:01.025 [notice] Opening Control listener on 127.0.0.1:0
Aug 30 12:08:01.026 [notice] Control listener listening on port 52975.
Aug 30 12:08:01.026 [notice] Opened Control listener connection (ready) on 127.0.0.1:52975
Aug 30 12:08:01.000 [notice] Parsing GEOIP IPv4 file /Users/berhart/Library/Developer/CoreSimulator/Devices/D3204428-26B1-4C55-8177-B3057F6F67AC/data/Containers/Bundle/Application/6DBEF322-E91E-4DF6-9058-F54252ED7E54/Tor-Example.app/Frameworks/Tor.framework/GeoIP.bundle/geoip.
Aug 30 12:08:01.000 [notice] Parsing GEOIP IPv6 file /Users/berhart/Library/Developer/CoreSimulator/Devices/D3204428-26B1-4C55-8177-B3057F6F67AC/data/Containers/Bundle/Application/6DBEF322-E91E-4DF6-9058-F54252ED7E54/Tor-Example.app/Frameworks/Tor.framework/GeoIP.bundle/geoip6.
Aug 30 12:08:01.000 [notice] Bootstrapped 0% (starting): Starting
Aug 30 12:08:14.000 [notice] Starting with guard context "default"
Aug 30 12:08:14.000 [warn] tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: Tor 0.4.8.4 (git-6d6bd21b9d364302): Line unexpectedly reached at relay_key_is_unavailable_ at ./src/feature/relay/routerkeys.h:56. Stack trace: (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 0 Tor 0x0000000101ed4254 log_backtrace_impl + 104 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 1 Tor 0x0000000101ee18ec tor_bug_occurred_ + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 2 Tor 0x0000000101e71580 server_onion_keys_new + 64 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 3 Tor 0x0000000101e133a0 worker_state_new + 48 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 4 Tor 0x0000000101ed857c threadpool_new + 256 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 5 Tor 0x0000000101e132d8 cpuworker_init + 128 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 6 Tor 0x0000000101e513c4 run_tor_main_loop + 200 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 7 Tor 0x0000000101e516bc tor_run_main + 312 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 8 Tor 0x00000001019c3a9c -[TORThread main] + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 9 Foundation 0x0000000180851578 __NSThread__start__ + 792 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 10 libsystem_pthread.dylib 0x00000001cc0b3428 _pthread_start + 116 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 11 libsystem_pthread.dylib 0x00000001cc0ae648 thread_start + 8 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: Tor 0.4.8.4 (git-6d6bd21b9d364302): Line unexpectedly reached at relay_key_is_unavailable_ at ./src/feature/relay/routerkeys.h:56. Stack trace: (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 0 Tor 0x0000000101ed4254 log_backtrace_impl + 104 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 1 Tor 0x0000000101ee18ec tor_bug_occurred_ + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 2 Tor 0x0000000101e71580 server_onion_keys_new + 64 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 3 Tor 0x0000000101e133a0 worker_state_new + 48 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 4 Tor 0x0000000101ed857c threadpool_new + 256 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 5 Tor 0x0000000101e132d8 cpuworker_init + 128 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 6 Tor 0x0000000101e513c4 run_tor_main_loop + 200 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 7 Tor 0x0000000101e516bc tor_run_main + 312 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 8 Tor 0x00000001019c3a9c -[TORThread main] + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 9 Foundation 0x0000000180851578 __NSThread__start__ + 792 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 10 libsystem_pthread.dylib 0x00000001cc0b3428 _pthread_start + 116 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 11 libsystem_pthread.dylib 0x00000001cc0ae648 thread_start + 8 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: Tor 0.4.8.4 (git-6d6bd21b9d364302): Line unexpectedly reached at relay_key_is_unavailable_ at ./src/feature/relay/routerkeys.h:56. Stack trace: (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 0 Tor 0x0000000101ed4254 log_backtrace_impl + 104 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 1 Tor 0x0000000101ee18ec tor_bug_occurred_ + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 2 Tor 0x0000000101e71580 server_onion_keys_new + 64 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 3 Tor 0x0000000101e133a0 worker_state_new + 48 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 4 Tor 0x0000000101ed857c threadpool_new + 256 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 5 Tor 0x0000000101e132d8 cpuworker_init + 128 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 6 Tor 0x0000000101e513c4 run_tor_main_loop + 200 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 7 Tor 0x0000000101e516bc tor_run_main + 312 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 8 Tor 0x00000001019c3a9c -[TORThread main] + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 9 Foundation 0x0000000180851578 __NSThread__start__ + 792 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 10 libsystem_pthread.dylib 0x00000001cc0b3428 _pthread_start + 116 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 11 libsystem_pthread.dylib 0x00000001cc0ae648 thread_start + 8 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: Tor 0.4.8.4 (git-6d6bd21b9d364302): Line unexpectedly reached at relay_key_is_unavailable_ at ./src/feature/relay/routerkeys.h:56. Stack trace: (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 0 Tor 0x0000000101ed4254 log_backtrace_impl + 104 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 1 Tor 0x0000000101ee18ec tor_bug_occurred_ + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 2 Tor 0x0000000101e71580 server_onion_keys_new + 64 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 3 Tor 0x0000000101e133a0 worker_state_new + 48 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 4 Tor 0x0000000101ed857c threadpool_new + 256 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 5 Tor 0x0000000101e132d8 cpuworker_init + 128 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 6 Tor 0x0000000101e513c4 run_tor_main_loop + 200 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 7 Tor 0x0000000101e516bc tor_run_main + 312 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 8 Tor 0x00000001019c3a9c -[TORThread main] + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 9 Foundation 0x0000000180851578 __NSThread__start__ + 792 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 10 libsystem_pthread.dylib 0x00000001cc0b3428 _pthread_start + 116 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 11 libsystem_pthread.dylib 0x00000001cc0ae648 thread_start + 8 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: Tor 0.4.8.4 (git-6d6bd21b9d364302): Line unexpectedly reached at relay_key_is_unavailable_ at ./src/feature/relay/routerkeys.h:56. Stack trace: (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 0 Tor 0x0000000101ed4254 log_backtrace_impl + 104 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 1 Tor 0x0000000101ee18ec tor_bug_occurred_ + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 2 Tor 0x0000000101e71580 server_onion_keys_new + 64 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 3 Tor 0x0000000101e133a0 worker_state_new + 48 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 4 Tor 0x0000000101ed857c threadpool_new + 256 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 5 Tor 0x0000000101e132d8 cpuworker_init + 128 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 6 Tor 0x0000000101e513c4 run_tor_main_loop + 200 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 7 Tor 0x0000000101e516bc tor_run_main + 312 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 8 Tor 0x00000001019c3a9c -[TORThread main] + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 9 Foundation 0x0000000180851578 __NSThread__start__ + 792 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 10 libsystem_pthread.dylib 0x00000001cc0b3428 _pthread_start + 116 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 11 libsystem_pthread.dylib 0x00000001cc0ae648 thread_start + 8 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: Tor 0.4.8.4 (git-6d6bd21b9d364302): Line unexpectedly reached at relay_key_is_unavailable_ at ./src/feature/relay/routerkeys.h:56. Stack trace: (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 0 Tor 0x0000000101ed4254 log_backtrace_impl + 104 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 1 Tor 0x0000000101ee18ec tor_bug_occurred_ + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 2 Tor 0x0000000101e71580 server_onion_keys_new + 64 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 3 Tor 0x0000000101e133a0 worker_state_new + 48 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 4 Tor 0x0000000101ed857c threadpool_new + 256 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 5 Tor 0x0000000101e132d8 cpuworker_init + 128 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 6 Tor 0x0000000101e513c4 run_tor_main_loop + 200 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 7 Tor 0x0000000101e516bc tor_run_main + 312 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 8 Tor 0x00000001019c3a9c -[TORThread main] + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 9 Foundation 0x0000000180851578 __NSThread__start__ + 792 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 10 libsystem_pthread.dylib 0x00000001cc0b3428 _pthread_start + 116 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 11 libsystem_pthread.dylib 0x00000001cc0ae648 thread_start + 8 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: Tor 0.4.8.4 (git-6d6bd21b9d364302): Line unexpectedly reached at relay_key_is_unavailable_ at ./src/feature/relay/routerkeys.h:56. Stack trace: (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 0 Tor 0x0000000101ed4254 log_backtrace_impl + 104 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 1 Tor 0x0000000101ee18ec tor_bug_occurred_ + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 2 Tor 0x0000000101e71580 server_onion_keys_new + 64 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 3 Tor 0x0000000101e133a0 worker_state_new + 48 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 4 Tor 0x0000000101ed857c threadpool_new + 256 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 5 Tor 0x0000000101e132d8 cpuworker_init + 128 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 6 Tor 0x0000000101e513c4 run_tor_main_loop + 200 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 7 Tor 0x0000000101e516bc tor_run_main + 312 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 8 Tor 0x00000001019c3a9c -[TORThread main] + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 9 Foundation 0x0000000180851578 __NSThread__start__ + 792 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 10 libsystem_pthread.dylib 0x00000001cc0b3428 _pthread_start + 116 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 11 libsystem_pthread.dylib 0x00000001cc0ae648 thread_start + 8 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: Tor 0.4.8.4 (git-6d6bd21b9d364302): Line unexpectedly reached at relay_key_is_unavailable_ at ./src/feature/relay/routerkeys.h:56. Stack trace: (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 0 Tor 0x0000000101ed4254 log_backtrace_impl + 104 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 1 Tor 0x0000000101ee18ec tor_bug_occurred_ + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 2 Tor 0x0000000101e71580 server_onion_keys_new + 64 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 3 Tor 0x0000000101e133a0 worker_state_new + 48 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 4 Tor 0x0000000101ed857c threadpool_new + 256 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 5 Tor 0x0000000101e132d8 cpuworker_init + 128 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 6 Tor 0x0000000101e513c4 run_tor_main_loop + 200 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 7 Tor 0x0000000101e516bc tor_run_main + 312 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 8 Tor 0x00000001019c3a9c -[TORThread main] + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 9 Foundation 0x0000000180851578 __NSThread__start__ + 792 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 10 libsystem_pthread.dylib 0x00000001cc0b3428 _pthread_start + 116 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 11 libsystem_pthread.dylib 0x00000001cc0ae648 thread_start + 8 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: Tor 0.4.8.4 (git-6d6bd21b9d364302): Line unexpectedly reached at relay_key_is_unavailable_ at ./src/feature/relay/routerkeys.h:56. Stack trace: (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 0 Tor 0x0000000101ed4254 log_backtrace_impl + 104 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 1 Tor 0x0000000101ee18ec tor_bug_occurred_ + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 2 Tor 0x0000000101e71580 server_onion_keys_new + 64 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 3 Tor 0x0000000101e133a0 worker_state_new + 48 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 4 Tor 0x0000000101ed857c threadpool_new + 256 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 5 Tor 0x0000000101e132d8 cpuworker_init + 128 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 6 Tor 0x0000000101e513c4 run_tor_main_loop + 200 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 7 Tor 0x0000000101e516bc tor_run_main + 312 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 8 Tor 0x00000001019c3a9c -[TORThread main] + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 9 Foundation 0x0000000180851578 __NSThread__start__ + 792 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 10 libsystem_pthread.dylib 0x00000001cc0b3428 _pthread_start + 116 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 11 libsystem_pthread.dylib 0x00000001cc0ae648 thread_start + 8 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] tor_bug_occurred_: Bug: ./src/feature/relay/routerkeys.h:56: relay_key_is_unavailable_: This line should not have been reached. (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: Tor 0.4.8.4 (git-6d6bd21b9d364302): Line unexpectedly reached at relay_key_is_unavailable_ at ./src/feature/relay/routerkeys.h:56. Stack trace: (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 0 Tor 0x0000000101ed4254 log_backtrace_impl + 104 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 1 Tor 0x0000000101ee18ec tor_bug_occurred_ + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 2 Tor 0x0000000101e71580 server_onion_keys_new + 64 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 3 Tor 0x0000000101e133a0 worker_state_new + 48 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 4 Tor 0x0000000101ed857c threadpool_new + 256 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 5 Tor 0x0000000101e132d8 cpuworker_init + 128 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 6 Tor 0x0000000101e513c4 run_tor_main_loop + 200 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 7 Tor 0x0000000101e516bc tor_run_main + 312 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 8 Tor 0x00000001019c3a9c -[TORThread main] + 324 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 9 Foundation 0x0000000180851578 __NSThread__start__ + 792 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 10 libsystem_pthread.dylib 0x00000001cc0b3428 _pthread_start + 116 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [warn] Bug: 11 libsystem_pthread.dylib 0x00000001cc0ae648 thread_start + 8 (on Tor 0.4.8.4 6d6bd21b9d364302)
Aug 30 12:08:14.000 [notice] New control connection opened from 127.0.0.1.
2023-08-30 12:08:14.446361+0200 Tor-Example[9047:362250] authenticated success=1
2023-08-30 12:08:14.446749+0200 Tor-Example[9047:362251] established=0
Aug 30 12:08:15.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Aug 30 12:08:15.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Aug 30 12:08:15.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Aug 30 12:08:15.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Aug 30 12:08:15.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Aug 30 12:08:15.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Aug 30 12:08:15.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Aug 30 12:08:16.000 [notice] Bootstrapped 100% (done): Done
2023-08-30 12:08:16.044047+0200 Tor-Example[9047:362251] established=1
2023-08-30 12:08:17.063880+0200 Tor-Example[9047:362251] Circuits: (
"<TORCircuit: 0x6000022ee530> circuitId=1, status=EXTENDED, nodes=(\n \"<TORNode: 0x600001c8d900> fingerprint=$2B1FF21E30BA75F43F696E0634489C806408E3F8, nickName=noWarPlz, ipv4Address=62.101.228.30, ipv6Address=(null), countryCode=no, localizedCountryName=Norway\",\n \"<TORNode: 0x600001c8d8c0> fingerprint=$9BA9334DA769A7C96D464F9EA38A970088B6FECB, nickName=FASHIONCLEFT, ipv4Address=95.217.223.54, ipv6Address=2a01:4f9:c010:9ed2::1, countryCode=fi, localizedCountryName=Finland\"\n), buildFlags=(\n \"NEED_CAPACITY\",\n \"NEED_UPTIME\"\n), purpose=CONFLUX_UNLINKED, hsState=(null), rendQuery=(null), timeCreated=2023-08-30 10:08:15 +0000, reason=(null), remoteReason=(null), socksUsername=(null), socksPassword=(null), raw=1 EXTENDED $2B1FF21E30BA75F43F696E0634489C806408E3F8~noWarPlz,$9BA9334DA769A7C96D464F9EA38A970088B6FECB~FASHIONCLEFT BUILD_FLAGS=NEED_CAPACITY,NEED_UPTIME PURPOSE=CONFLUX_UNLINKED TIME_CREATED=2023-08-30T10:08:15.450637]",
"<TORCircuit: 0x6000022ee5a0> circuitId=2, status=EXTENDED, nodes=(\n \"<TORNode: 0x600001c944c0> fingerprint=$780004EAD7B2B96C26AB320713BAAA7BC246B862, nickName=salentrakain, ipv4Address=185.195.237.116, ipv6Address=(null), countryCode=ee, localizedCountryName=Estonia\",\n \"<TORNode: 0x600001c945c0> fingerprint=$E04861C32098EF38D6BB2AEFEC81095953FEF0ED, nickName=willwallace, ipv4Address=95.217.72.151, ipv6Address=2a01:4f9:4a:1812::2, countryCode=fi, localizedCountryName=Finland\"\n), buildFlags=(\n \"NEED_CAPACITY\",\n \"NEED_UPTIME\"\n), purpose=CONFLUX_UNLINKED, hsState=(null), rendQuery=(null), timeCreated=2023-08-30 10:08:15 +0000, reason=(null), remoteReason=(null), socksUsername=(null), socksPassword=(null), raw=2 EXTENDED $780004EAD7B2B96C26AB320713BAAA7BC246B862~salentrakain,$E04861C32098EF38D6BB2AEFEC81095953FEF0ED~willwallace BUILD_FLAGS=NEED_CAPACITY,NEED_UPTIME PURPOSE=CONFLUX_UNLINKED TIME_CREATED=2023-08-30T10:08:15.459137]",
"<TORCircuit: 0x6000022ee8b0> circuitId=3, status=BUILT, nodes=(\n \"<TORNode: 0x600001c94540> fingerprint=$2B1FF21E30BA75F43F696E0634489C806408E3F8, nickName=noWarPlz, ipv4Address=62.101.228.30, ipv6Address=(null), countryCode=no, localizedCountryName=Norway\",\n \"<TORNode: 0x600001c94740> fingerprint=$EEA85567CD7EBEB1CBC70AEE97C45E0019BDBDF9, nickName=jstark1809n0n0n0, ipv4Address=194.32.107.206, ipv6Address=2a03:94e0:ffff:194:32:107:0:206, countryCode=no, localizedCountryName=Norway\",\n \"<TORNode: 0x600001c947c0> fingerprint=$4E60DE549B3B4C063E6035BCDAA69DD4F3AE3C4D, nickName=Chimera2, ipv4Address=149.56.22.133, ipv6Address=2607:5300:61:785::, countryCode=ca, localizedCountryName=Canada\"\n), buildFlags=(\n \"NEED_CAPACITY\"\n), purpose=GENERAL, hsState=(null), rendQuery=(null), timeCreated=2023-08-30 10:08:15 +0000, reason=(null), remoteReason=(null), socksUsername=(null), socksPassword=(null), raw=3 BUILT $2B1FF21E30BA75F43F696E0634489C806408E3F8~noWarPlz,$EEA85567CD7EBEB1CBC70AEE97C45E0019BDBDF9~jstark1809n0n0n0,$4E60DE549B3B4C063E6035BCDAA69DD4F3AE3C4D~Chimera2 BUILD_FLAGS=NEED_CAPACITY PURPOSE=GENERAL TIME_CREATED=2023-08-30T10:08:15.463437]"
)
2023-08-30 12:08:17.075981+0200 Tor-Example[9047:362251] Elapsed Time: 1.031664
```
### What is the expected behavior?
Bug not happening.
### Environment
- Which version of Tor are you using? See first lines of log. 0.4.8.4
- Which operating system are you using? For example: iOS 15.5 in simulator, macOS Ventura 13.5.1
- Which installation method did you use? Git; see "steps to reproduce"
### Relevant logs and/or screenshots
### Possible fixesAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41317gitlab is slow(er than usual)2023-09-11T18:09:44Zanarcatgitlab is slow(er than usual)this morning gitlab slowed to a crawl. multiple users reported the site being barely usable, and i didn't even file an incident here at the time because it was so slow, filing this as a post-mortem.this morning gitlab slowed to a crawl. multiple users reported the site being barely usable, and i didn't even file an incident here at the time because it was so slow, filing this as a post-mortem.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/prometheus-alerts/-/issues/11Fix Tor DNS EL Freshness description2023-09-11T16:59:05ZGeorg KoppenFix Tor DNS EL Freshness description`Tor DNS EL Freshness` moves into `UNSTABLE` [after 180 minutes of staleness](https://gitlab.torproject.org/tpo/network-health/metrics/monitoring-and-alerting/-/blob/c0bdcde3099d4252be0890ef34497227a7cee87b/data/check#L28), not 60 as the...`Tor DNS EL Freshness` moves into `UNSTABLE` [after 180 minutes of staleness](https://gitlab.torproject.org/tpo/network-health/metrics/monitoring-and-alerting/-/blob/c0bdcde3099d4252be0890ef34497227a7cee87b/data/check#L28), not 60 as the alert implies.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41316Please add rhatto@ to network-team@2023-09-11T15:51:00ZAlexander Færøyahf@torproject.orgPlease add rhatto@ to network-team@Please add rhatto@ to the network-team@ email alias so he can get updates on team stuff.Please add rhatto@ to the network-team@ email alias so he can get updates on team stuff.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/131Moat distributor is sharing offline bridges2023-09-11T14:42:44ZGusMoat distributor is sharing offline bridgesMoat is distributing obfs4 bridges that are currently offline. By checking their fingerprint on Metrics, it appears that these bridges no longer exist.
Reported via Tor forum: https://forum.torproject.org/t/bridges-requested-in-tb-do-...Moat is distributing obfs4 bridges that are currently offline. By checking their fingerprint on Metrics, it appears that these bridges no longer exist.
Reported via Tor forum: https://forum.torproject.org/t/bridges-requested-in-tb-do-not-work-only-the-ones-built-in/9172/2meskiomeskio@torproject.orgmeskiomeskio@torproject.orghttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/136Modify the bridge scanner API to be the same as bridgestrap2023-09-11T08:08:52ZjugaModify the bridge scanner API to be the same as bridgestrapbridgestrap API: https://gitlab.torproject.org/tpo/anti-censorship/bridgestrap#inputbridgestrap API: https://gitlab.torproject.org/tpo/anti-censorship/bridgestrap#inputjugajuga