[tor-relays] cannot update respository
Hello: I hope you can help. My bridge is offline because: Please upgrade! This version of Tor (0.4.2.7) is not recommended, according to the directory authorities. Recommended versions are: 0.3.5.10,0.3.5.11,0.3.5.12,0.3.5.13,0.4.3.3-alpha,0.4.3.4-rc,0.4.3.5,0.4.3.6,0.4.3.7,0.4.3.8,0.4.4.1-alpha,0.4.4.2-alpha,0.4.4.3-alpha,0.4.4.4-rc,0.4.4.5,0.4.4.6,0.4.4.7,0.4.5.1-alpha,0.4.5.2-alpha,0.4.5.3-rc,0.4.5.4-rc,0.4.5.5-rc,0.4.5.6 When I try to update it I get this: darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:~$ lsb_release -c Codename: ulyssa darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:~$ cd /etc/apt/sources.list bash: cd: /etc/apt/sources.list: Not a directory darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:~$ cd /etc/apt/sources.list.d/ darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ sudo nano /etc/apt/sources.list.d darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ ls official-package-repositories.list tor-project.list darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ sudo nano /etc/apt/sources.list.d/ darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ lsb_release -c Codename: ulyssa darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ sudo nano /etc/apt/sources.list.d/ darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ wget -qO- https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc | gpg --import gpg: key EE8CBC9E886DDD89: 83 signatures not checked due to missing keys gpg: error writing keyring '/home/darkhoodie/.gnupg/pubring.kbx': Permission denied gpg: error reading '[stdin]': Permission denied gpg: import from '[stdin]' failed: Permission denied gpg: Total number processed: 0 darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ sudo wget -qO- https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc | gpg --import gpg: key EE8CBC9E886DDD89: 83 signatures not checked due to missing keys gpg: error writing keyring '/home/darkhoodie/.gnupg/pubring.kbx': Permission denied gpg: error reading '[stdin]': Permission denied gpg: import from '[stdin]' failed: Permission denied gpg: Total number processed: 0 darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ sudo gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | apt-key add - gpg: directory '/root/.gnupg' created gpg: keybox '/root/.gnupg/pubring.kbx' created gpg: WARNING: nothing exported E: This command can only be used by root. darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ sudo apt update Ign:1 http://packages.linuxmint.com ulyssa InRelease Hit:2 http://packages.linuxmint.com ulyssa Release Hit:3 http://archive.canonical.com/ubuntu focal InRelease Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease Hit:6 http://archive.ubuntu.com/ubuntu focal InRelease Hit:7 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:8 http://archive.ubuntu.com/ubuntu focal-backports InRelease Ign:9 https://deb.torproject.org/torproject.org ulyssa InRelease Err:10 https://deb.torproject.org/torproject.org ulyssa Release 404 Not Found [IP: 95.216.163.36 443] Reading package lists... Done N: Ignoring file 'sources.list.d' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension E: The repository 'https://deb.torproject.org/torproject.org ulyssa Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:/etc/apt/sources.list.d$ Not sure where I'm going wrong. Please help. Thank you___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] tor on Ubuntu Server 20.04.2 LTS
Hi All, Which version of tor runs on Ubuntu Server 20.04.2 LTS 64bit, if any? Thanks matt ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor on Rpi
Hello Patrice would be great if you can share your script , thanks. signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor relay failed to start after upgrade (0.4.4.6 --> 0.4.5.5) [solved]
On 09 Feb (11:55:12), tscha...@posteo.de wrote: > Tonight my Tor relay on Raspberry Pi (buster) was upgraded from > 0.4.4.6-1~bpo10+1 to 0.4.5.5-rc-1~bpo10+1 automaticly, but failed to start: > > --- > [notice] Opening OR listener on 0.0.0.0:587 > [notice] Opened OR listener connection (ready) on 0.0.0.0:587 > [notice] Opening OR listener on [::]:587 > [warn] Socket creation failed: Address family not supported by protocol > [notice] Opening Directory listener on 0.0.0.0:995 > [notice] Closing partially-constructed OR listener connection (ready) on > 0.0.0.0:587 > [notice] Closing partially-constructed Directory listener connection (ready) > on 0.0.0.0:995 > --- > > Until then there was no change in my torrc: > > ORPort 587 > DIRPORT 995 Oh wow, interesting, so your Pi doesn't support IPv6 for some reasons and it failed to start with this config. I have opened: https://gitlab.torproject.org/tpo/core/tor/-/issues/40283 In 0.4.5.x tor, things have changed where tor will try to auto discover an IPv6 and automatically bind to it if only "ORPort " is used. In other words, it now binds to 0.0.0.0 and [::] by default. It then publish any discovered _usable_ and _reachable_ IPv4/IPv6. If it doesn't find any IPv6, it will still listen but won't publish any IPv6. > > It seems the value [address:] is no longer optional if you're not IPv6 ready > [1]: > > ORPort [address:]PORT|auto [flags] > DirPort [address:]PORT|auto [flags] > > So I have to change my torrc to: > > ORPort 0.0.0.0:587 > DIRPORT 0.0.0.0:995 Another option would have been to add the "IPv4Only" flag to the ORPort line and should have done it for you. Cheers! David -- YrY9JHvSOJpDfyKS5AyL8h/BjZ/SQEkh00q9ek+1BXk= signature.asc Description: PGP signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Can't connect to bridge after rebuilding server
OK, I *CAN* connect to the 443 port bridge using the new cert and the
original fingerprint, just like port 80. So I'm not sure why the bridge
status page reports what it does.
So, my question is still, is there a way to get my new configuration to
rebuild itself to use the previous certs.
Cheers.
On 2/8/2021 10:30 PM, Roger Dingledine wrote:
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 hangs.
The ports on the VPS are open. I can see an ESTABLISHED connection from
home, but the browser just hangs throwing out this: [WARN] Proxy Client:
unable to connect to aaa.bbb.ccc.ddd:443 ("general SOCKS server failure")
Not sure what to check next.
It looks like the "vanilla ORPort" part of your bridge works (I just
bootstrapped my Tor through it to confirm), but your obfs4 port is
busted somehow:
https://bridges.torproject.org/status?id=8BBAB62EA65E47CDF204E3D795DAD12E5046EB72
https://lists.torproject.org/pipermail/tor-relays/2021-January/019221.html
I wonder if, when you restored things, you also restored the obfs4
keys?
It looks like OhNoAnotherBridge80 is doing better?
https://bridges.torproject.org/status?id=B080140DC1BAB5B86D1CE5A4CA2EF64F20282440
--Roger
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
--
This e-mail was checked for spam by the freeware edition of CleanMail.
The freeware edition is restricted to personal and non-commercial use.
You can remove this notice by purchasing a commercial license:
http://antispam.byteplant.com/products/cleanmail/index.html
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Can't connect to bridge after rebuilding server
Ha. I copied the complete keys directory from my old configuration to
the new, hoping everything would be the same. But I didn't realise that
the cert used in the connection string would now be different. Using
the new cert and original fingerprint I can now connect over the port 80
bridge. Is there any way to revert back to the original cert, so that
the folks who already have the bridge configured can use it as they
always have.
Let me look at what might be wrong with the 443 port, but I did exactly
the same "shift and drop" technique for both the bridges.
Cheers.
On 2/8/2021 10:30 PM, Roger Dingledine wrote:
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 hangs.
The ports on the VPS are open. I can see an ESTABLISHED connection from
home, but the browser just hangs throwing out this: [WARN] Proxy Client:
unable to connect to aaa.bbb.ccc.ddd:443 ("general SOCKS server failure")
Not sure what to check next.
It looks like the "vanilla ORPort" part of your bridge works (I just
bootstrapped my Tor through it to confirm), but your obfs4 port is
busted somehow:
https://bridges.torproject.org/status?id=8BBAB62EA65E47CDF204E3D795DAD12E5046EB72
https://lists.torproject.org/pipermail/tor-relays/2021-January/019221.html
I wonder if, when you restored things, you also restored the obfs4
keys?
It looks like OhNoAnotherBridge80 is doing better?
https://bridges.torproject.org/status?id=B080140DC1BAB5B86D1CE5A4CA2EF64F20282440
--Roger
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
--
This e-mail was checked for spam by the freeware edition of CleanMail.
The freeware edition is restricted to personal and non-commercial use.
You can remove this notice by purchasing a commercial license:
http://antispam.byteplant.com/products/cleanmail/index.html
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
