tor-browser-build issueshttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues2024-01-26T17:00:01Zhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41068Build error Tor Browser Android for F-Droid: printf2024-01-26T17:00:01ZMynacolBuild error Tor Browser Android for F-Droid: printfI try to compile Tor Browser Android with F-Droid, but hit a hard wall. Compiling according to the docs and without containers works in a fresh Debian 11 container.
Running about the same commands with F-Droid build leads to a curious er...I try to compile Tor Browser Android with F-Droid, but hit a hard wall. Compiling according to the docs and without containers works in a fresh Debian 11 container.
Running about the same commands with F-Droid build leads to a curious error message while trying to compile node. I tried the build process multiple times, even on a fresh bare-metal Debian 11 installation, with always the same error message. Here it is:
```
make[1]: printf: Argument list too long
```
The full logs can be found [here](https://nowtransfer.de/acf4781c8d68) (GitLab was not happy about the file size).
And the F-Droid build script for these logs is [here](https://gitlab.com/Mynacol/fdroiddata/-/blob/9637d788d272b4c827e5225d5806a7c9f19b96d1/metadata/org.torproject.torbrowser.yml) while the newest build script might be found [in the branch](https://gitlab.com/Mynacol/fdroiddata/-/blob/add-torbrowser/metadata/org.torproject.torbrowser.yml).
My suspicion is that make calls the printf program and either make, the shell or printf is unhappy about the argument size. And the argument size might be bigger, because the absolute paths are in the F-Droid build longer, as they are done in `/fdroiddata/build/org.torproject.torbrowser/...`.
Ping to https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/27539MynacolMynacolhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41060tor browser memory leak2024-01-09T15:00:34Zcypherpunkstor browser memory leakWhen I leave tor browser running its using all the memory like a memory leak.
Im just displaying https://myip.wtf/ so its not the website itself.
It was a huge problem 2021 or 2022.
After a while I noticed that it got fixed.... Im not s...When I leave tor browser running its using all the memory like a memory leak.
Im just displaying https://myip.wtf/ so its not the website itself.
It was a huge problem 2021 or 2022.
After a while I noticed that it got fixed.... Im not sure exactly when.
But now the problem is back again.
And this time Im making a proper bugreport.
Im using 13.0.8 and have following extentions installed:
* Adblock Plus - Free AD blocker
* Bookmark Tab Here
* NoScript
And no not running these extentions is not an alternative.
Im using Linux.
I really want to have this solved and can be of help to solve it.cypherpunkscypherpunkshttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40883Verification issues with the new Windows code signing certificate2023-08-17T21:35:26Zcypherpunks1Verification issues with the new Windows code signing certificateThe new certificate cannot be verified on two systems that I tried it.
A comparison of the 12.0.4 and 12.5a7 installers:
![cert](/uploads/eceecebe2d7a455900271857d7484f25/cert.png)The new certificate cannot be verified on two systems that I tried it.
A comparison of the 12.0.4 and 12.5a7 installers:
![cert](/uploads/eceecebe2d7a455900271857d7484f25/cert.png)cypherpunks1cypherpunks1https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40630Update builtin bridges from Circumvention Settings API2022-12-22T11:22:11Zmeskiomeskio@torproject.orgUpdate builtin bridges from Circumvention Settings APIRight now to update the builtin bridges we need to make a Tor Browser release, it would be nice if TB automatically updates them using [Circumvention Settings API](https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/blob/main/doc/m...Right now to update the builtin bridges we need to make a Tor Browser release, it would be nice if TB automatically updates them using [Circumvention Settings API](https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/blob/main/doc/moat.md#circumventionbuiltin).
There are two concerns I have about it:
* Users will not be happy with TB making a call to an external API without giving some consent about it.
* We don't want to make easier for censors to notice you are using Tor because of that.
I think it makes sense to update when we do other connections to moat (Connect Assist, captcha bridges, ...), I assume user has already consent to do a request to the API on those cases and having an extra connection over the domain fronting should not make it more noticeable than it already is. We could store when was the last time we had updated them, and don't update them is they are fresh (maybe 24h is a good freshness).
An extra that would be nice is to ask the user if they want to refresh the builtin bridges when they click on Settings to *Select a Built-In Bridge*. I think we should only ask if bridges hasn't being refreshed for a while (maybe 7days). The confirmation popup could have a check box with 'remember that option' or something like that, so the following times they enable builtin bridges we refresh or not without asking (if the bridges hasn't being refreshed in 7days).Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibethttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/26895'Error downloading build result' after GCC in container Tor Browser Bundle Bu...2022-08-02T15:31:54ZTrac'Error downloading build result' after GCC in container Tor Browser Bundle Build (rbm)... most descriptive error ever ocurred in the world $ make
git submodule update --init
./rbm/rbm build release --target release --target torbrowser-all
Building project tor-browser - tor-browser-8.0a9-linux-x86_64-58eca3
Using file out/container-image/container-image_w... $ make
git submodule update --init
./rbm/rbm build release --target release --target torbrowser-all
Building project tor-browser - tor-browser-8.0a9-linux-x86_64-58eca3
Using file out/container-image/container-image_wheezy-amd64-df3a332e7b34.tar.gz
Building project firefox - firefox-a0efd2fcd6e9-linux-x86_64-0974b5
Tag tor-browser-60.1.0esr-8.0-1-build2 is signed with key 35CD74C24A9B15A19E1A81A194373AA94B7C3223
Created tmp/rbm-mgl5M/firefox-a0efd2fcd6e9.tar.gz
Using file out/container-image/container-image_wheezy-amd64-279bd3a261cd.tar.gz
Building project gcc - gcc-6.4.0-3098e6.tar.gz
Using file out/container-image/container-image_wheezy-amd64-2bf0a6561acb.tar.gz
Using file out/gcc/gcc-6.4.0.tar.xz
[sudo] password for $USER:
Build log: logs/gcc-linux-x86_64.log
[sudo] password for $USER:
Error: Error downloading build result
make: *** [Makefile:6: release] Error 1
Thats the log on the screen...
**Trac**:
**Username**: kfseapersonhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/26877Declare gcc version in rbm.conf2021-08-18T08:57:02ZSukhbir SinghDeclare gcc version in rbm.confWe declare the `gcc` version (currently set to `6.4.0`) in multiple places:
```
projects/gcc/config:version: 6.4.0
```
```
projects/mingw-w64/config: gcc_version: 6.4.0
```
We should probably define it in `rbm.conf` instead and then ...We declare the `gcc` version (currently set to `6.4.0`) in multiple places:
```
projects/gcc/config:version: 6.4.0
```
```
projects/mingw-w64/config: gcc_version: 6.4.0
```
We should probably define it in `rbm.conf` instead and then refer to that. (This may also be relevant for legacy/trac#25485).https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/23688Add GitLab CI script2021-08-16T20:44:30ZTracAdd GitLab CI scriptAs [suggested and merged for tor](https://trac.torproject.org/projects/tor/ticket/22891) I'd like to propose a GitLab CI script for Tor Browser. My intention to be able to build `tor-browser-bundle` locally which I tried for some time an...As [suggested and merged for tor](https://trac.torproject.org/projects/tor/ticket/22891) I'd like to propose a GitLab CI script for Tor Browser. My intention to be able to build `tor-browser-bundle` locally which I tried for some time and failed because of error which I hope will be brought to the attention of devs automatically rather than after painful reports.
The script currently uses Ubuntu 17.04 only, but since GitLab CI is based on Docker images, the number of possible OS to test on is basically infinite.
**Trac**:
**Username**: krichterhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/18497Check that MAR signing is done properly on the files available in the update ...2023-01-31T20:39:12ZboklmCheck that MAR signing is done properly on the files available in the update responsesIn legacy/trac#18405 we are adding a script to be used during the release process to check that the MAR files are properly signed. We could have an other one that is doing the same things on the files currently proposed as an update. Thi...In legacy/trac#18405 we are adding a script to be used during the release process to check that the MAR files are properly signed. We could have an other one that is doing the same things on the files currently proposed as an update. This would allow someone to easily check (maybe as a cron job) that the updates currently available are the same as the ones in the sha256sums-unsigned-build files.
In tools/update-responses/check_update_responses_deployement we have a script that currently check that the update responses xml provides the expected version. I think I could extend it to also download the mar files it provides, unsign them and check that they match sha256sums-unsigned-build.txt.