[tor-relays] Bridge not used
Hi Tor-Operators, I have installed a bridge according to the official how-to. The config is as follows: Log notice file /var/log/tor/notices.log DataDirectory /var/lib/tor Address bridge.xxx.de BridgeRelay 1 ORPort 1044 ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy ServerTransportListenAddr obfs4 0.0.0.0:9043 ExtORPort auto ContactInfo arn...@mailbox.org Nickname lunabridge PublishServerDescriptor 1 BridgeDistribution any Under https://metrics.torproject.org/rs.html#details/4DD98FB1959065309FD4A183530BC915A689E493 I see basically no usage, the logs are fine - as far as I can tell. Any help appreciated! Best, Arnim ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Bridge not used
Hi,
It's because your bridge is not being distributed ("Bridge distribution
mechanism reserved").
Change to another bridge distribution method: https, email...
See this Support article:
https://support.torproject.org/relay-operators/change-bridge-distribution/
Thanks for running bridges!
Gus
On Tue, May 10, 2022 at 02:40:14PM +0200, Arnim Wiezer via tor-relays wrote:
> Hi Tor-Operators,
>
> I have installed a bridge according to the official how-to. The config is as
> follows:
>
> Log notice file /var/log/tor/notices.log
> DataDirectory /var/lib/tor
> Address bridge.xxx.de
> BridgeRelay 1
> ORPort 1044
> ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
> ServerTransportListenAddr obfs4 0.0.0.0:9043
> ExtORPort auto
> ContactInfo arn...@mailbox.org
> Nickname lunabridge
> PublishServerDescriptor 1
> BridgeDistribution any
>
> Under
> https://metrics.torproject.org/rs.html#details/4DD98FB1959065309FD4A183530BC915A689E493
>
> I see basically no usage, the logs are fine - as far as I can tell.
>
> Any help appreciated!
>
> Best,
> Arnim
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
--
The Tor Project
Community Team Lead
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] Bridge not used
On 5/10/22 14:57, gus wrote:
It's because your bridge is not being distributed ("Bridge distribution
mechanism reserved").
Change to another bridge distribution method: https, email...
See this Support article:
https://support.torproject.org/relay-operators/change-bridge-distribution/
I think this line can be removed from your torrc "BridgeDistribution
any", I guess then it defaults to something, I assume to https.
Is that correct?
Regards
yl
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Ext Relay Operators: Please Upgrade to 0.4.7.7!
On 5/4/22 4:31 PM, Mike Perry wrote: > Tor 0.4.7.7-stable contains a very important performance improvement, > called Congestion Control. > We have packages in available for Debian, Ubuntu, Fedora, CentOS, and > BSD: > - Debian: https://support.torproject.org/apt/tor-deb-repo/ > - Ubuntu: https://support.torproject.org/relay-operators/operators-4/ > - Fedora/CentOS: https://support.torproject.org/rpm/tor-rpm-install/ > - BSD: > https://lists.torproject.org/pipermail/tor-relays/2022-May/020528.html Anyone know when the EPEL TOR packages will updated? The EL 8 repos only offer 0.4.5.11. EL 9 is only a little newer with RPMs for TOR 0.4.6.8. Fedora 35 and 36 (with the latter launching today) have only been updated to 0.4.6.9. As of now, it appears that only Fedora 37 has been updated to 0.4.7.7. Yes, I know, there is a 0.4.7.7 RPM for EL 8 inside the TOR repo, but I'm wondering if anyone knows when the Fedora/EPEL repos will be updated? Anu more importantly why they haven't been updated already? When I compared the packages from EPEL and TOR a couple of years ago (both offered the sane TOR release at that point) I discovered the TOR package was built differently - assuming thta is still the case, it means the RPMs aren't interchangeable for someone with a torrc file that has evolved beyond the default. Fedora repo for the TOR package: https://src.fedoraproject.org/rpms/tor Drect download Link for the TOR repo RPM in case anyone wants it: https://rpm.torproject.org/centos/8/x86_64/tor-0.4.7.7-1.el8.x86_64.rpm L~ ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Ext Relay Operators: Please Upgrade to 0.4.7.7!
On Tuesday, May 10, 2022 4:55:57 PM CEST Ladar Levison via tor-relays wrote: > Anyone know when the EPEL TOR packages will updated? The EL 8 repos only > offer 0.4.5.11. EL 9 is only a little newer with RPMs for TOR 0.4.6.8. > Fedora 35 and 36 (with the latter launching today) have only been > updated to 0.4.6.9. As of now, it appears that only Fedora 37 has been > updated to 0.4.7.7. I don't know the philosophy of Fedora/EPEL (CentOS/RHEL). In general, no configuration-breaking software is installed on productive systems. With debian, once the release is frozen and stable, there are _no_ upgrades. This is the main reason for the stable archive! There are only updates, security updates in the 'stable main' archive Some new features are offered in backports if they don't break configs of stable packages. There are very few upgrades (virus scanners and timezone data) in stable-updates, formerly volatile. Therefore, Tor upgrades with new features must be installed from the Tor project repro. EPEL (CentOS/RHEL) may have a similar policy and you must grab packages from the Tor project if you want to upgrade. -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom! signature.asc Description: This is a digitally signed message part. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Debian is not allowing tor to update despite it being listed as a trusted respritory
On Saturday, May 7, 2022 6:50:43 PM CEST Keifer Bly wrote: > Ok will try these things. Does that it's an ovh debain have anything to do > with it? Hosted by them and they may frown on tor. No, there are a lot (actually too many) Tor relays at OVH. https://nusenu.github.io/OrNetStats/#autonomous-systems-by-cw-fraction -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom! signature.asc Description: This is a digitally signed message part. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Debian is not allowing tor to update despite it being listed as a trusted respritory
On Monday, May 9, 2022 9:40:12 AM CEST ben wrote: Hi, I think this mail should reach Keifer. @ Keifer please post the output of: cat /etc/issue It should be 'Debian GNU/Linux 10' apt update && sudo apt full-upgrade would install missing packages. Then read what Ben wrote about 'update-ca-certificates'. -- Forwarded Message -- Subject: Re: [tor-relays] Debian is not allowing tor to update despite it being listed as a trusted respritory Date: Donnerstag, 5. Mai 2022, 15:09:07 CEST From: ben To: tor-relays CC: lists > Simply displays a message "no valid openpgp data found". My sources file You'll see this because your system doesn't trust the cert chain. You're not seeing a certificate warning because you've got output suppressed (the -q in wget's arguments) If you run wget https://deb.torproject.org/torproject.org/ A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc I suspect you'll see the certificate warning. You need to fix that before anything suggested here is going to work - if the cert chain isn't trusted then apt isn't going to access the repository's indexes, and so won't even see what packages are there, much less install them. As apt didn't grab an updated version for you (which may be due to other repo misconfigurations) you probably want to grab and install the cert manually # Verify that this gives a cert warning curl https://deb.torproject.org/torproject.org/ curl -k --output "/tmp/ISRG_Root_X1.crt" "https://letsencrypt.org/certs/ isrgrootx1.pem.txt" sudo mv /tmp/ISRG_Root_X1.crt /usr/local/share/ca-certificates/ sudo update-ca-certificates # Now try again curl https://deb.torproject.org/torproject.org/ If that final curl now works, run apt-get update and you should find apt no longer complains about the tor repo -- Ben Tasker https://www.bentasker.co.uk -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom! signature.asc Description: This is a digitally signed message part. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Bridge not used
On Tue, May 10, 2022 at 03:08:16PM +0200, yl wrote:
>
> On 5/10/22 14:57, gus wrote:
> > It's because your bridge is not being distributed ("Bridge distribution
> > mechanism reserved").
> >
> > Change to another bridge distribution method: https, email...
> > See this Support article:
> > https://support.torproject.org/relay-operators/change-bridge-distribution/
>
> I think this line can be removed from your torrc "BridgeDistribution any", I
> guess then it defaults to something, I assume to https.
>
> Is that correct?
>
No, the distribution method is assigned by bridgeDB/rdsys and there isn't a
default method.
> Regards
> yl
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
--
The Tor Project
Community Team Lead
signature.asc
Description: PGP signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] OpenBSD -stable net/tor and 0.4.7.7
The OpenBSD net/tor -current port is correctly on 0.4.7.7, but the -stable port is still on 0.4.6.10. I submitted a diff to update -stable port to 0.4.7.7 last week, but it has not been committed yet. https://marc.info/?l=openbsd-ports&m=165179875418235&w=2 It's attached and should work fine. In order to update the OpenBSD -stable port you need an updated -stable 7.1 ports tree, then you apply the patch within the /usr/ports/net/tor port, and build from there. I can provide more guidance if necessary, but in order to not bore everyone else, maybe the Tor-BSD list is more appropriate? https://lists.nycbug.org:8443/mailman/listinfo/tor-bsd I can send out an amd64 -stable package, but then you'd have to trust me. gIndex: tor/Makefile === RCS file: /cvs/ports/net/tor/Makefile,v retrieving revision 1.143 diff -u -p -r1.143 Makefile --- tor/Makefile 11 Mar 2022 19:47:52 - 1.143 +++ tor/Makefile 6 May 2022 00:52:06 - @@ -1,6 +1,6 @@ COMMENT= anonymity service using onion routing -DISTNAME= tor-0.4.6.10 +DISTNAME= tor-0.4.7.7 CATEGORIES= net HOMEPAGE= https://www.torproject.org/ Index: tor/distinfo === RCS file: /cvs/ports/net/tor/distinfo,v retrieving revision 1.116 diff -u -p -r1.116 distinfo --- tor/distinfo 1 Mar 2022 10:29:07 - 1.116 +++ tor/distinfo 6 May 2022 00:52:06 - @@ -1,2 +1,2 @@ -SHA256 (tor-0.4.6.10.tar.gz) = lMzWDgTlWPM75zAyvITqJBZg+S9Yz7iHib2miTc54xw= -SIZE (tor-0.4.6.10.tar.gz) = 7811644 +SHA256 (tor-0.4.7.7.tar.gz) = PhMRWLUrlDXX5D0cR+8oi5bQBTQsxEuMlQu0A4UaW0Q= +SIZE (tor-0.4.7.7.tar.gz) = 7895089 Index: tor/patches/patch-configure_ac === RCS file: /cvs/ports/net/tor/patches/patch-configure_ac,v retrieving revision 1.18 diff -u -p -r1.18 patch-configure_ac --- tor/patches/patch-configure_ac 11 Mar 2022 19:47:53 - 1.18 +++ tor/patches/patch-configure_ac 6 May 2022 00:52:06 - @@ -2,7 +2,7 @@ disable -fasynchronous-unwind-tables as Index: configure.ac --- configure.ac.orig +++ configure.ac -@@ -1567,13 +1567,6 @@ fi +@@ -1435,13 +1435,6 @@ fi CFLAGS="$saved_CFLAGS" AC_SUBST(F_OMIT_FRAME_POINTER) ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
