A few years ago, I tried compiling Tor Browser from source on ARM and it failed because there was what looked like a binary blob that couldn’t be used on ARM. I remember asking on the tor-talk mailing list about this and the answer that I was given was that the Tor Browser developers have a specific build system that only works for Intel-based machines.
I would like to know what does the Tor Browser Dev team need in order to port it to ARM and other architectures like the new RISC-V architecture? Do you need more test hardware, do you need more experts in those architectures, do you need more volunteer developers? What can the community do to help with this?
I haven’t tried my ARM branch of Tor Browser on an RPi (I don’t have one; I’m testing on an Asus C201 and an Asus C100), but feel free to test it out and let me know how it goes. Let me know if you need help testing.
I don’t know what Tails’s plans are regarding non-x86 architectures. I believe the Whonix devs are favorable (I run Whonix on my ppc64le system as a daily driver).
Which OS are you running on your RPi 4? (In particular, is it armhf or arm64?) Are you comfortable building from source on an x86_64 machine, or do you prefer that I provide a binary for you? (Note that if I give you a binary, it’ll be one that was built on Cyberia infrastructure that isn’t under my physical control, so while I don’t think it’s dangerous, I cannot personally vouch for the safety of the binary. My preference is that you build from source, but I’m a flexible person and if you really want a binary, I can get you one.)