Request for Tor to support armhf architecture
I am running a Raspberry Pi Raspbian OS (debian) mini computer. Tor software does not support this hardware without me having to compile it myself for my platform. Which I don't know how to do. My specific APT error message says this: N: Skipping acquire of configured file 'main/binary-armhf/Packages' as repository 'https://deb.torproject.org/torproject.org bookworm InRelease' doesn't support architecture 'armhf' The Raspberry Pi is a perfect computer to run Tor because it has 8 GB RAM, is tiny, only uses a max of 25 watts of power and works great as a network server. Plus, I don't have to leave my big power hungry desktop computer on all the time to run Tor. Raspberry Pi info page: https://www.raspberrypi.com/products/raspberry-pi-5/ Landon
On Sat, 17 Aug 2024 19:35:46 -0600 Landon <reply@mynetblog.com> wrote:
The Raspberry Pi is a perfect computer to run Tor because it has 8 GB RAM, is tiny, only uses a max of 25 watts of power and works great as a network server. Plus, I don't have to leave my big power hungry desktop computer on all the time to run Tor.
If you have an RPi with 8GB of RAM you have either a RPi4 or RPi5. They both have aarch64/arm64-capable processors, and many Linux distros with support for this arch have aarch64 packages of the Tor daemon you can use + deb.torproject.org has aarch64 builds for bookworm. I suggest installing a aarch64 OS, Raspberry Pi OS has aarch64 images for example. -- Current PGP KeyID: 0AFB427F1800FD89751C4035292228735AE707FF https://blueselene.com/pgp-archive/0AFB427F1800FD89751C4035292228735AE707FF/...
On Mon, Aug 19, 2024 at 3:46 AM Alex <alex@blueselene.com> wrote:
If you have an RPi with 8GB of RAM you have either a RPi4 or RPi5. They both have aarch64/arm64-capable processors, and many Linux distros with support for this arch have aarch64 packages of the Tor daemon you can use + deb.torproject.org has aarch64 builds for bookworm.
I suggest installing a aarch64 OS, Raspberry Pi OS has aarch64 images for example.
This is the output of "uname -a" Linux pi 6.6.31+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64 GNU/Linux I was using aarch64 when I tried to install Tor from deb.torproject.org. I was able to install Tor from the debian archives instead. However, as I have found out over the years that I have been running a Tor server, Debian does not always have the latest version of Tor. Sometimes Debian is so out of date that Tor suggests that people don't use my Tor server. (For my production Tor server, I am running a VPS with Debian and Tor packages from deb.torproject.org) My APT config: deb [signed-by=/usr/share/keyrings/tor-archive-keyring.gpg] https://deb.torproject.org/torproject.org bookworm main deb-src [signed-by=/usr/share/keyrings/tor-archive-keyring.gpg] https://deb.torproject.org/torproject.org bookworm main I could install Tor from source, but keeping it up to date is not easy. Plus, I don't really know how to keep it up to date like that. I am running a Raspberry Pi 5 8 GB RAM model. https://www.raspberrypi.com/products/raspberry-pi-5/ I highly recommend that everyone get one because it is inexpensive, is a badass little computer and is a fun toy!! Plus the Pi 5 has a PCIe header where you can attach an NVMe drive. I bought this case designed for a NVMe M.2 drive: https://thepihut.com/products/argon-neo-5-m-2-nvme-case-for-raspberry-pi-5
Hi Landon,
but keeping it up to date is not easy. Plus, I don't really know how to keep it up to date like that. You check for a tor update every month or three, download the latest archive, compile and install that and as soon as you restart tor, it'll be up to date.
It being a package in a package manager is of course much more convenient - I've noticed tor is always kept reasonably up to date in Gentoo-libre myself.
I highly recommend that everyone get one because it is inexpensive, is a badass little computer and is a fun toy!! My personal recommendation is to never purchase a RPi unless it is supported by libre-rpi, as unless you are running libre-rpi, RPi's follow broadcom's orders before yours, considering that they're controlled by proprietary software running on the VPU.
A real computer that can be GNUbooted and doesn't restrict you from doing anything you want (via refusal to provide the source code under a free license) is a much funner toy to me. -- Kind Regards, DiffieHellman
Hi Landon, Aarch64 is a supported architecture for tor, although it appears there isn't a buildbot for binaries. It'll be easiest to just compile from source, which I'll help you with. First you install dependencies and fine GNU software (I'm guessing some of the dependency names, as debian-based distros have the bad habit of stripping the headers from libraries (very small files that allow you to compile things) and putting them in -dev named packages, or even worse under another name); sudo apt install libevent-dev openssl-dev libcap-dev libseccomp-dev gnupg wget gcc make tar asciidoc Download tor; `wget https://dist.torproject.org/tor-0.4.8.12.tar.gz https://dist.torproject.org/tor-0.4.8.12.tar.gz.sha256sum https://dist.torproject.org/tor-0.4.8.12.tar.gz.sha256sum.asc` Check that the archive isn't corrupted; `sha256sum -c tor-0.4.8.12.tar.gz.sha256sum` Check that the archive hasn't been tampered with; `gpg --verify tor-0.4.8.12.tar.gz.sha256sum.asc` The keys won't be in your keyring, so you'll get; gpg: using RSA key B74417EDDF22AC9F9E90F49142E86A2A11F48D36 gpg: Can't check signature: No public key gpg: using EDDSA key 514102454D0A87DB0767A1EBBE6A0531C18A917 gpg: Can't check signature: No public key But you can just import them; `gpg --recv-keys B74417EDDF22AC9F9E90F49142E86A2A11F48D36 514102454D0A87DB0767A1EBBE6A0531C18A9179` gpg: key BEA7B180B1491921: public key "Alexander Færøy <ahf@0x90.dk>" imported gpg: key 42E86A2A11F48D36: 1 duplicate signature removed gpg: key 42E86A2A11F48D36: public key "David Goulet <dgoulet@ev0ke.net>" imported Then you can verify (the GNU bash command to repeat the command before last is `!-2`); `gpg --verify tor-0.4.8.12.tar.gz.sha256sum.asc`; The important part is "Good signature", the "WARNING" part is due to there not beng a web of trust. Then extract the archive; tar xf tor-0.4.8.12.tar.gz (GNU tar gives no output on success, but returns 0 - you can check the return code of the immediately previous command with `echo $?`). Don't need the archive or signature anymore; `rm tor-0.4.8.12.tar.gz*` `cd tor-0.4.8.12` Then configure; `./configure` The command may fail and tell you that a dependency is missing - to fix that you install that dependency and try again until all dependencies are installed. Then it is time to compile; `make -j$(nproc)` Compiling should not fail, but if so, gcc will tell you why. Finally, (optionally) install with; `sudo make install`. -- Kind Regards, DiffieHellman
participants (3)
-
Alex -
DiffieHellman -
Landon