The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-11-20T16:40:54Zhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41327Disable UrlbarProviderInterventions2023-11-20T16:40:54ZPier Angelo VendrameDisable UrlbarProviderInterventions@cypherpunks1 said that urlbar interventions are not disabled in Tor Browser, and that the preference we are using (`browser.urlbar.update1.interventions`) is obsolete (see https://gitlab.torproject.org/tpo/applications/tor-browser/-/iss...@cypherpunks1 said that urlbar interventions are not disabled in Tor Browser, and that the preference we are using (`browser.urlbar.update1.interventions`) is obsolete (see https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40783#note_2838323).
I am not familiar with this part of Firefox. From a quick search, I found that they can be still disabled with enterprise policies.
We should check why we disabled them in the first place, if it's still needed, or if we can keep them enabled.Sponsor 131 - Phase 2 - Privacy Browserrichardrichardhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41085Refactor the UI to remove all bridges2023-05-01T12:53:10ZdonutsRefactor the UI to remove all bridgesIn #40782 we introduced the concept of bridge cards. As part of that work, we provided a means to remove all bridge cards using a red button positioned below the bridge stack:
- [remove-all-bridges](/uploads/3c9cf520633386ed07bc35ee6341...In #40782 we introduced the concept of bridge cards. As part of that work, we provided a means to remove all bridge cards using a red button positioned below the bridge stack:
- [remove-all-bridges](/uploads/3c9cf520633386ed07bc35ee63418704/remove-all-bridges.png)
However it shares the same position as the "Show all bridges" button, which was terrible UX on my part. We should consider improving this.Sponsor 30 - Objective 3.5Dan BallardDan Ballard2023-04-17https://gitlab.torproject.org/tpo/web/blog/-/issues/40060To publish: blog post about DDoS attack2023-02-06T19:53:58ZIsabela FernandesTo publish: blog post about DDoS attacktitle: Tor is slow right now. Here is what is happening.
author: Isabela
# Why Tor is slow right now and what we are doing about it.
For at least 7 months, several different types of ongoing denial of service (DoS) attacks have affect...title: Tor is slow right now. Here is what is happening.
author: Isabela
# Why Tor is slow right now and what we are doing about it.
For at least 7 months, several different types of ongoing denial of service (DoS) attacks have affected the Tor network. At some points, the attacks impacted the network severely enough that users could not load pages or access onion services.
We have been working hard to mitigate the impacts and defend the network from these attacks. The methods and targets of these attacks have changed over time and we are adapting as these attacks continue. It's not possible to determine with certainty who is conducting these attacks or their intentions.
We will continue to increase and tweak defenses on the Tor network to combat this problem. We are also adding two new members to our Network team who will be solely focused on .onion services development.
# A big thank you to our community.
We know that a lot of people use and depend on Tor for security and privacy while connecting to the internet. There are many tools and pieces of infrastructure out there that depend on Tor as well. We take that responsibility and the work we do very seriously.
The Tor Project has a strong community that also understands Tor’s importance for so many people around the world, and fortunately, they have always been there to help.
Throughout our work to improve the network’s defenses, many people have stepped up to support us, fight this attack, and make sure the Tor network is stable for users. Allies have [highlighted the importance of financially supporting Tor](https://bitcoinmagazine.com/culture/if-you-love-bitcoin-you-should-help-tor), [held fundraisers to add more relays to the network](https://savetor.network/), [funded current relay operator associations](https://bitcoinmagazine.com/business/hrf-awards-325000-bitcoin-grants), and come together to form the Onion Services Resource Coalition, which has allowed us to hire two new network team developers who will focus specifically on onion services. This, plus the countless supporters who have spread the word about helping Tor on social media and in their communities.
We would like to add to this post a big thank you to everyone in our community—and to our friends at [Ocelot](https://ocelot.net/), [Quiet](https://tryquiet.org/), [Wasabi Wallet / zKSNACKs](https://zksnacks.com/), [Fedimint](https://fedimint.org/), [Trezor](https://trezor.io/), [OpenSats](https://opensats.org/), and [Freedom of the Press Foundation](https://freedom.press/)—who are helping us right now in all sorts of ways, we thank you.
# You can help too! Here is how:
We are 70% towards our goal of fully funding two years worth of onion service development to mitigate the impacts of these attacks. **We have $155,000 left to raise.**
If you believe in the importance of the Tor network and defending it against attacks, please make a donation directly towards this work:
- [Make a USD donation via Stripe or PayPal](https://donate.torproject.org/): add “onion services” to the comments field.
- [Make a BTC donation via BTCPayServer](https://btcpay.torproject.org/apps/48eCC1sFqByBXTKKoCgMmkkGvheX/pos): we’ll know your donation is to be used to advance onion services.
- [Make a cryptocurrency donation directly to our wallet](https://donate.torproject.org/cryptocurrency/): let us know you’ve made a donation at giving at torproject.org
You can contribute to the Onion Support Coalition fund by making a donation.
If you have any information that could help us understand better the nature of these attacks you can contact us via signal: [https://signal.me/#p/+17787431312](https://signal.me/#p/+17787431312).
If you are a relay operator and would like to know more about what to do to defend your relay from these types of attacks you can connect with us through the email list tor-relays at lists.torproject.org. We actually recommend that all relay operators join this list to be up to date with best practices to keep the Tor network healthy.https://gitlab.torproject.org/tpo/web/blog/-/issues/40056Update our 2023 event calendar2023-02-13T21:05:44ZRoger DingledineUpdate our 2023 event calendarHere is a start at some events we should tell the world we are interested in:
* FOSDEM, Brussels, Feb 4-5
https://fosdem.org/2023/
* RightsCon, Costa Rica, Jun 5-8
https://www.rightscon.org/attend/
* Mozfest, Amsterdam, Jun 8-20
https...Here is a start at some events we should tell the world we are interested in:
* FOSDEM, Brussels, Feb 4-5
https://fosdem.org/2023/
* RightsCon, Costa Rica, Jun 5-8
https://www.rightscon.org/attend/
* Mozfest, Amsterdam, Jun 8-20
https://www.mozillafestival.org/en/proposals/
* PETS, Switzerland, Jul 10-14
https://petsymposium.org/
* Usenix Security, California, Aug 9-11
https://www.usenix.org/conference/usenixsecurity23
* Defcon, Las Vegas, Aug 10-13
https://defcon.org/html/defcon-31/dc-31-cfi.html
* Internet Governance Forum, Japan, Oct 8-12
https://www.intgovforum.org/en/content/igf-2023
Let's collect whichever ones are missing, and then get them added as events on the blog calendar, and also tell Al and the newsletter people so they can get included in the right newsletters, and also plan to tweet about them at the right times.https://gitlab.torproject.org/tpo/web/tpo/-/issues/367removing digital defenders from sponsors page2023-02-08T22:01:16ZBekeela Davilaremoving digital defenders from sponsors pagePlease update the sponsors page https://www.torproject.org/about/sponsors/ to remove digital defenders. I have made this change and would like for someone to make the changes live.
https://gitlab.torproject.org/bekeela/tpo/-/blob/master...Please update the sponsors page https://www.torproject.org/about/sponsors/ to remove digital defenders. I have made this change and would like for someone to make the changes live.
https://gitlab.torproject.org/bekeela/tpo/-/blob/master/content/about/sponsors/Digital%20Defenders/.gitkeep
commit: d9977222ead8b29321b31584748f81b21131f4b6
Thank you and please let me know if I didn't do this correctly.https://gitlab.torproject.org/tpo/web/donate-static/-/issues/108Remove YEC match language from donate.tpo2023-02-08T03:37:17Zal smithRemove YEC match language from donate.tpoI forgot to mention that the "Your donation will be matched by Friends of Tor, up to $100,000" + donate button should be removed from donate.torproject.org when I filed my other closing YEC tickets. Could this be removed? The header bann...I forgot to mention that the "Your donation will be matched by Friends of Tor, up to $100,000" + donate button should be removed from donate.torproject.org when I filed my other closing YEC tickets. Could this be removed? The header banner can/should stay, just remove the text + button.
![Screen_Shot_2023-01-31_at_12.57.31_PM](/uploads/f624d64c08d0e0b9755f581b852d7602/Screen_Shot_2023-01-31_at_12.57.31_PM.png)https://gitlab.torproject.org/tpo/tpa/team/-/issues/41121Eugeni greylisting own our services2023-06-07T16:47:49ZJérôme Charaouilavamind@torproject.orgEugeni greylisting own our servicesWhile working on email deliverability tests in the context of tpo/tpa/team#41063, I noticed that `eugeni` was greylisting mail sent from servers in our own infrastructure.
And indeed, looking at the postgrey configuration in `/etc/postg...While working on email deliverability tests in the context of tpo/tpa/team#41063, I noticed that `eugeni` was greylisting mail sent from servers in our own infrastructure.
And indeed, looking at the postgrey configuration in `/etc/postgrey`, we see it's exempting `debian.org` machines, but not our own...
So I think we should add a `torproject.org` entry in `/etc/postgrey/whitelist_clients` on `eugeni`, and manage those configs through Puppet.
This will ensure that services relaying mail though `eugeni` (Discourse, GitLab, RT, CiviCRM...) aren't needlessly delayed.improve mail servicesJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40984New build machine for nightlies2023-07-17T07:57:59ZrichardNew build machine for nightliesSo we have this interesting situation where it takes longer than a day to build all of our browser nightlies, and this situation is only going to worsen once we add privacy-browser to the mix.
I think another machine with the same specs...So we have this interesting situation where it takes longer than a day to build all of our browser nightlies, and this situation is only going to worsen once we add privacy-browser to the mix.
I think another machine with the same specs as `tb-build-04` would be sufficient, but we should probably run some verify that.
@micah Do you think we could get funding approval for this?
/cc @pierov @boklmanarcatanarcat2023-06-07https://gitlab.torproject.org/tpo/tpa/team/-/issues/41155Ensure emails from weather-01 are DKIM-signed2023-06-08T13:14:22ZJérôme Charaouilavamind@torproject.orgEnsure emails from weather-01 are DKIM-signedCurrently, the Tor Weather platform on `weather-01` is sending emails as `weather@torproject.org` but they're not DKIM-signed so its likely there might be some deliverability issues for these notifications.Currently, the Tor Weather platform on `weather-01` is sending emails as `weather@torproject.org` but they're not DKIM-signed so its likely there might be some deliverability issues for these notifications.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41142Retire metrics-psqlts-012023-06-12T16:13:11ZJérôme Charaouilavamind@torproject.orgRetire metrics-psqlts-01The metrics team has finished experimenting with victoriametrics and would like to move on to a new production deployment.
1. [x] announcement (N/A)
2. [x] nagios
3. [x] retire the host in fabric
4. [x] remove from LDAP with `ldapvi...The metrics team has finished experimenting with victoriametrics and would like to move on to a new production deployment.
1. [x] announcement (N/A)
2. [x] nagios
3. [x] retire the host in fabric
4. [x] remove from LDAP with `ldapvi`
5. [x] power-grep
6. [x] remove from tor-passwords
7. [x] remove from DNSwl (N/A)
8. [x] remove from docs
9. [x] remove from racks (N/A)
10. [x] remove from reverse DNSJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41207Puppet broken on buster systems2023-06-12T19:53:02ZJérôme Charaouilavamind@torproject.orgPuppet broken on buster systemsThe few remaining Debian `buster` systems have received an LTS update to the Ruby 2.5 libraries this week, but it turns out this update has broken the Puppet agents.
The problem has already been brought to the attention of the Debian LT...The few remaining Debian `buster` systems have received an LTS update to the Ruby 2.5 libraries this week, but it turns out this update has broken the Puppet agents.
The problem has already been brought to the attention of the Debian LTS team via [bug #1037178](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037178) and it seems like a fix is already in the works.
Affected machines:
- alberti.torproject.org
- cupani.torproject.org
- eugeni.torproject.org
- hetzner-hel1-01.torproject.org
- pauli.torproject.org
- vineale.torproject.orgDebian 11 bullseye upgradeJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40044Comments are broken on onion version2023-06-26T16:53:02ZsreadyComments are broken on onion versionWhen visiting some post through onion service ([example](http://pzhdfe7jraknpj2qgu5cz2u3i4deuyfwmonvzu5i3nyw4t4bmg7o5pad.onion/new-alpha-release-tor-browser-120a1/)) with JS enabled, there is a browser error instead of comments section. ...When visiting some post through onion service ([example](http://pzhdfe7jraknpj2qgu5cz2u3i4deuyfwmonvzu5i3nyw4t4bmg7o5pad.onion/new-alpha-release-tor-browser-120a1/)) with JS enabled, there is a browser error instead of comments section. Looks related to CSP.Sponsor 9 - Phase 6 - Usability and Community Intervention on Support for Democracy and Human RightsJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.org2023-06-30https://gitlab.torproject.org/tpo/tpa/team/-/issues/41236gitolite: Redirect tor.git to Gitlab2023-06-26T16:15:35ZDavid Gouletdgoulet@torproject.orggitolite: Redirect tor.git to GitlabHello,
Network team is ready to have `tor.git` on Gitolite to be redirected to Gitlab and thus become canonical repository:
https://gitweb.torproject.org/tor.git -> https://gitlab.torproject.org/tpo/core/tor
Thanks!Hello,
Network team is ready to have `tor.git` on Gitolite to be redirected to Gitlab and thus become canonical repository:
https://gitweb.torproject.org/tor.git -> https://gitlab.torproject.org/tpo/core/tor
Thanks!legacy Git infrastructure retirement (TPA-RFC-36)Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41240btcpayserver-02 not in nagios?2023-06-26T18:59:13ZJérôme Charaouilavamind@torproject.orgbtcpayserver-02 not in nagios?`btcpayserver-02` is not monitored in Nagios. Is that intentional, or an oversight?
I could not find any explanation about this in the previous tickets related to that server's setup.`btcpayserver-02` is not monitored in Nagios. Is that intentional, or an oversight?
I could not find any explanation about this in the previous tickets related to that server's setup.anarcatanarcathttps://gitlab.torproject.org/tpo/web/team/-/issues/39merge the two web wikis2023-07-04T19:16:14Zanarcatmerge the two web wikisi hadn't realized this, but we have two web wikis. that is bad. let's not do that and merge them both... here?
https://gitlab.torproject.org/tpo/web/wiki/-/wikis/home
https://gitlab.torproject.org/tpo/web/team/-/wikis/home
/cc @emmapeeli hadn't realized this, but we have two web wikis. that is bad. let's not do that and merge them both... here?
https://gitlab.torproject.org/tpo/web/wiki/-/wikis/home
https://gitlab.torproject.org/tpo/web/team/-/wikis/home
/cc @emmapeelanarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41226network port misconfiguration on dal-sw-012023-07-06T18:13:53Zanarcatnetwork port misconfiguration on dal-sw-01I've been trying to use a third port on our server named dal-node-03 and it seems there's no carrier on the port:
```
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP mode DEFAULT group default qlen 1000
...I've been trying to use a third port on our server named dal-node-03 and it seems there's no carrier on the port:
```
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP mode DEFAULT group default qlen 1000
link/ether 3c:ec:ef:d5:6a:e8 brd ff:ff:ff:ff:ff:ff
altname eno1np0
altname enp200s0f0np0
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 3c:ec:ef:d5:6a:e9 brd ff:ff:ff:ff:ff:ff
altname eno2np1
altname enp200s0f1np1
4: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 3c:ec:ef:c0:1b:6a brd ff:ff:ff:ff:ff:ff
altname enp129s0f0
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 3c:ec:ef:c0:1b:6b brd ff:ff:ff:ff:ff:ff
altname enp129s0f1
```
I have logged into the Switch's web interface and confirm the "operational port status" is "Link Down".
I've also noticed that port #3 on dal-node-03 is connected to port 11 on the switch instead of the expected 12, at least as far as I can tell from here. dal-node-02 has a similar misconfiguration.
Here's the status of LLDP discovery on the two affected servers:
```
root@dal-node-02:~# lldpcli show neighbors
-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------
Interface: eth0, via: LLDP, RID: 1, Time: 0 day, 00:00:50
Chassis:
ChassisID: mac 28:f1:0e:f2:b3:28
SysName: dal-sw-01
Port:
PortID: ifname Gi1/0/5
PortDescr: dal-node-02, port 1
TTL: 120
-------------------------------------------------------------------------------
Interface: eth1, via: LLDP, RID: 1, Time: 0 day, 00:00:46
Chassis:
ChassisID: mac 28:f1:0e:f2:b3:28
SysName: dal-sw-01
Port:
PortID: ifname Gi1/0/6
PortDescr: dal-node-02, port 2
TTL: 120
-------------------------------------------------------------------------------
Interface: eth2, via: LLDP, RID: 1, Time: 0 day, 00:00:50
Chassis:
ChassisID: mac 28:f1:0e:f2:b3:28
SysName: dal-sw-01
Port:
PortID: ifname Gi1/0/8
PortDescr: dal-node-02, port 4
TTL: 120
-------------------------------------------------------------------------------
Interface: eth3, via: LLDP, RID: 1, Time: 0 day, 00:00:49
Chassis:
ChassisID: mac 28:f1:0e:f2:b3:28
SysName: dal-sw-01
Port:
PortID: ifname Gi1/0/7
PortDescr: dal-node-02, port 3
TTL: 120
-------------------------------------------------------------------------------
root@dal-node-02:~#
```
```
root@dal-node-03:~# lldpcli show neighbors
-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------
Interface: eth0, via: LLDP, RID: 3, Time: 0 day, 00:47:26
Chassis:
ChassisID: mac 28:f1:0e:f2:b3:28
SysName: dal-sw-01
Port:
PortID: ifname Gi1/0/9
PortDescr: dal-node-03, port 1
TTL: 120
-------------------------------------------------------------------------------
Interface: eth1, via: LLDP, RID: 3, Time: 0 day, 00:47:26
Chassis:
ChassisID: mac 28:f1:0e:f2:b3:28
SysName: dal-sw-01
Port:
PortID: ifname Gi1/0/10
PortDescr: dal-node-03, port 2
TTL: 120
-------------------------------------------------------------------------------
Interface: eth3, via: LLDP, RID: 3, Time: 0 day, 00:45:54
Chassis:
ChassisID: mac 28:f1:0e:f2:b3:28
SysName: dal-sw-01
Port:
PortID: ifname Gi1/0/11
PortDescr: dal-node-03, port 3
TTL: 120
-------------------------------------------------------------------------------
root@dal-node-03:~#
```
Here's the correct configuration, on the first server:
```
root@dal-node-01:~# lldpcli show neighbors
-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------
Interface: eth0, via: LLDP, RID: 1, Time: 6 days, 03:22:41
Chassis:
ChassisID: mac 28:f1:0e:f2:b3:28
SysName: dal-sw-01
Port:
PortID: ifname Gi1/0/1
PortDescr: dal-node-01, port 1
TTL: 120
-------------------------------------------------------------------------------
Interface: eth1, via: LLDP, RID: 1, Time: 6 days, 03:22:42
Chassis:
ChassisID: mac 28:f1:0e:f2:b3:28
SysName: dal-sw-01
Port:
PortID: ifname Gi1/0/2
PortDescr: dal-node-01, port 2
TTL: 120
-------------------------------------------------------------------------------
Interface: eth2, via: LLDP, RID: 1, Time: 0 day, 00:05:27
Chassis:
ChassisID: mac 28:f1:0e:f2:b3:28
SysName: dal-sw-01
Port:
PortID: ifname Gi1/0/3
PortDescr: dal-node-01, port 3
TTL: 120
-------------------------------------------------------------------------------
Interface: eth3, via: LLDP, RID: 1, Time: 0 day, 00:05:48
Chassis:
ChassisID: mac 28:f1:0e:f2:b3:28
SysName: dal-sw-01
Port:
PortID: ifname Gi1/0/4
PortDescr: dal-node-01, port 4
TTL: 120
-------------------------------------------------------------------------------
root@dal-node-01:~#
```
I managed to recover port 12 by re-enabling auto-negociation. For some reason it was hardcoded to 1000mbps in the switch interface, switching that to auto fixed the link. But then it negociated at 100mbps. There's a couple more ports that sync at that speed as well.
So it looks like autonegociation is failing with the Intel gigabit cards.
We're looking at moving storage traffic to those new ports because that we're having extremely odd and worrisome corruption issue on the storage VLAN (#41176).
So this needs to happen here:
- [x] swap port 3 and 4 on dal-node-02 (or confirm they are correctly wired), ports 8 and 7 on the switch
- [x] swap port 3 and 4 on dal-node-03 (or confirm they are correctly wired), ports 12 and 11 on the switch
- [x] replace cable on port 12
- [x] fix autonegociation on all ports to have 1000mbps (gigabit!)anarcatanarcat2023-07-06https://gitlab.torproject.org/tpo/tpa/team/-/issues/41204update arma's gpg key2023-06-05T20:17:57ZRoger Dingledineupdate arma's gpg keyI have a new gpg subkey, and I think the way to get that key updated here is to file a gitlab ticket. This is that ticket! Thanks.
[0xF65CE37F04BA5B360AE6EE17C218525819F78451.asc](/uploads/6d6bdfe56af5b99ef71035dd551020f7/0xF65CE37F04BA...I have a new gpg subkey, and I think the way to get that key updated here is to file a gitlab ticket. This is that ticket! Thanks.
[0xF65CE37F04BA5B360AE6EE17C218525819F78451.asc](/uploads/6d6bdfe56af5b99ef71035dd551020f7/0xF65CE37F04BA5B360AE6EE17C218525819F78451.asc)Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41108build a new VM to deploy donate-neo review environments2023-09-20T00:55:55ZKezbuild a new VM to deploy donate-neo review environmentscontext: tpo/web/donate-neo#6
donate-neo needs a place to deploy CI environments. we'll do this by creating a new server named donate-review-01, with 8G memory, 2 vCPU cores, 10G root, 2G swap, and 20G HDD. thw software stack for the re...context: tpo/web/donate-neo#6
donate-neo needs a place to deploy CI environments. we'll do this by creating a new server named donate-review-01, with 8G memory, 2 vCPU cores, 10G root, 2G swap, and 20G HDD. thw software stack for the review deployments will be apache, mod_wsgi, python 3.10, and sqlite.
as for the deployment procedure, i was thinking of having the CI pipeline build an installable package and scp it to the donate-review-01 box, SSH in, and call a script. this script will set up a virtual environment, install the required packages, and create a new apache config and restart apache.
@anarcat do those VM specs and deployment steps look good to you?https://gitlab.torproject.org/tpo/applications/mullvad-browser/-/issues/32Update Signing Scripts to support Mullvad Browser2023-03-15T12:25:48ZrichardUpdate Signing Scripts to support Mullvad Browserboklmboklmhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/29834Update Google Play screenshots2022-12-09T15:20:07ZMatthew FinkelUpdate Google Play screenshotsWe should show the new bootstrap/configuration UI. Maybe we should wait until the animation is working, too.We should show the new bootstrap/configuration UI. Maybe we should wait until the animation is working, too.richardrichard2022-12-02