Hi everyone! Here is my status report for May 2022.
Part of my work this month was again on Android. I finally resolved the crash we had for a while [0] in 11.0.13, or so I hope 😁. So far, all users have told us that they do not encounter that problem anymore, so please let us know if it is not the case for you. I also helped prepare and release the two releases and the two alphas we had this month (11.0.12, 11.0.13, 11.5a10, and 11.5a12). Other improvements on my side are that now testbuilds are single architecture (so they are much faster to build) [1], and all the QA APKs we produce are now compatible with Android 10+ [2].
For desktop, I updated some of our patches to make them easier to upstream to Firefox, and I have already sent them to Mozilla [3]. Some were accepted, some are still being reviewed, and a pair was rejected. I also set everything up to include an offline copy of the Tor Browser manual in the bundle and accessible within the browser [4]. Finally, I fixed some minor issues on the work done in the previous months on the about:torconnect page and on the connection settings.
Thanks, Pier
[0] https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40212 [1] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40... [2] https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40202 [3] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40917 [4] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11698
Can you add the bugzilla links for the upstreaming? I wonder if I've missed some of them...
On Wed, 1 Jun 2022 at 05:24, Pier Angelo Vendrame pierov@torproject.org wrote:
Hi everyone! Here is my status report for May 2022.
Part of my work this month was again on Android. I finally resolved the crash we had for a while [0] in 11.0.13, or so I hope 😁. So far, all users have told us that they do not encounter that problem anymore, so please let us know if it is not the case for you. I also helped prepare and release the two releases and the two alphas we had this month (11.0.12, 11.0.13, 11.5a10, and 11.5a12). Other improvements on my side are that now testbuilds are single architecture (so they are much faster to build) [1], and all the QA APKs we produce are now compatible with Android 10+ [2].
For desktop, I updated some of our patches to make them easier to upstream to Firefox, and I have already sent them to Mozilla [3]. Some were accepted, some are still being reviewed, and a pair was rejected. I also set everything up to include an offline copy of the Tor Browser manual in the bundle and accessible within the browser [4]. Finally, I fixed some minor issues on the work done in the previous months on the about:torconnect page and on the connection settings.
Thanks, Pier
[0] https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40212 [1] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40... [2] https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40202 [3] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40917 [4] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11698 _______________________________________________ tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
On 6/1/22 15:39, Tom Ritter wrote:
Can you add the bugzilla links for the upstreaming? I wonder if I've missed some of them...
Hi, sure!
https://bugzilla.mozilla.org/show_bug.cgi?id=1768899: This was rejected earlier, because users are not expected to modify the changes the patch deals with.
https://bugzilla.mozilla.org/show_bug.cgi?id=1769028: So far, only the priority has been assigned to this bug. I am more than willing to do anything the triage owner will ask me.
https://bugzilla.mozilla.org/show_bug.cgi?id=1429838: This was started almost two years ago, so before I started working at Tor. If I understood correctly, all the reviewer's comments were addressed, but one remains as to be solved. I added a comment that I would like to continue the process to get the patch merged, or to address any other remaining problems with it.
https://bugzilla.mozilla.org/show_bug.cgi?id=1768907: I have attached our patch to the bug, and it was assigned to a Mozilla developer, but I am more than willing to help in any way.
https://bugzilla.mozilla.org/show_bug.cgi?id=1711084#c15: I have attached our patch to the bug. However, the proof of concept for that vulnerability uses different code for Firefox and for Tor Browser, so it may not work for Firefox.
https://bugzilla.mozilla.org/show_bug.cgi?id=1769030: This has been approved by one reviewer, I am waiting for the second one.
https://bugzilla.mozilla.org/show_bug.cgi?id=1433509: This is an old ticket and was already marked as a wontfix. The wontfix decision has been approved. It makes sense, because that code seems to be dead (I have tried to add a #error on the code, but it did not make the build fail).
https://bugzilla.mozilla.org/show_bug.cgi?id=1769250: This does not allow us to drop a patch, but at least to drop the changes we did to the related file. Anyway, it was merged.
https://bugzilla.mozilla.org/show_bug.cgi?id=1475811: This is not for an upstream, but to see if Firefox's problem still exists, and if we can improve directly upstream.
A few months ago I opened a GitLab issue to track all the uplift requests: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40789. I am continuing to update it for new issues.
Cheers,
Pier
On Wed, 1 Jun 2022 at 05:24, Pier Angelo Vendrame pierov@torproject.org wrote:
Hi everyone! Here is my status report for May 2022.
Part of my work this month was again on Android. I finally resolved the crash we had for a while [0] in 11.0.13, or so I hope 😁. So far, all users have told us that they do not encounter that problem anymore, so please let us know if it is not the case for you. I also helped prepare and release the two releases and the two alphas we had this month (11.0.12, 11.0.13, 11.5a10, and 11.5a12). Other improvements on my side are that now testbuilds are single architecture (so they are much faster to build) [1], and all the QA APKs we produce are now compatible with Android 10+ [2].
For desktop, I updated some of our patches to make them easier to upstream to Firefox, and I have already sent them to Mozilla [3]. Some were accepted, some are still being reviewed, and a pair was rejected. I also set everything up to include an offline copy of the Tor Browser manual in the bundle and accessible within the browser [4]. Finally, I fixed some minor issues on the work done in the previous months on the about:torconnect page and on the connection settings.
Thanks, Pier
[0] https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40212 [1] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40... [2] https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40202 [3] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40917 [4] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11698 _______________________________________________ tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
tor-project@lists.torproject.org