On Sun, Feb 07, 2021 at 10:44:53AM -0500, tor wrote:
> When I do the following command:
>
> :~ $ sudo gpg --keyserver keys.gnupg.net --recv
> A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89
>
> I get:
>
> gpg: packet(13) too large
> gpg: read_block: read error: Invalid packet
> gpg: no valid OpenPGP
On Sat, Feb 06, 2021 at 12:31:29PM -, relay.jack...@simplelogin.fr wrote:
> im running a tor relay on rpi 2 with version 0.4.2.7., on the Tor relay
> search i see my relay is outdated and flaged as not recomended, however on
> rpi i have tried update and upgrade many times and always get
On Mon, Feb 08, 2021 at 06:58:55PM -0800, Eddie wrote:
> Following the rebuild, the bridges
> appear to start correctly, according to both the logs and
> https://metrics.torproject.org/rs.html#search/OhNoAnotherBridge. However
> attempting to connect via the tor browser from my home system just
I had to rebuild my VPS today. Before doing so, I copied off everything
I thought I needed to rebuild my bridges. Following the rebuild, the
bridges appear to start correctly, according to both the logs and
https://metrics.torproject.org/rs.html#search/OhNoAnotherBridge. However
attempting
Hi,
I am also have a tor relay running, but on a RPI 4. No long time ago I
stood at the same point as you are now. I than wrote me a skript, where it:
1. pulls the latest source
2. backs up the old data (identity)
3. compiles and installs tor
4. copies the old data on the new installation
5.
Try this commands:
1. curl
https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc
| gpg --import
2. gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
After that try (sudo apt-key list) OR (gpg --list-keys) should list the updated
key.
Hello
im running a tor relay on rpi 2 with version 0.4.2.7., on the Tor relay search
i see my relay is outdated and flaged as not recomended, however on rpi i have
tried update and upgrade many times and always get notification from apt that
tor i already de newest version, also tried apt
