On Fri, Oct 14, 2022 at 06:08:38PM +0200, Toralf Förster wrote:
> On 10/14/22 11:28, meskio wrote:
> > The latest version of obfs4proxy (0.0.14) comes with an important security
> > fix.
>
> Is there a Changelog available ?
The below issue, which is currently confidential, has details of what
wa
Hi there,
Am 16.10.22 um 17:09 schrieb Anonforpeace via tor-relays:
Hello:
My Tor Bridge has been down for awhile as I was moving to a new home. I
have been trying to bring it up again and have been receiving the
messages you see below. I have checked the the tor project status and
see tha
Hi,
Bridges are usually not impacted by network-wide DoS as they are not
as public as any other node.
Your node thinks it's unreachable. Have you confirmed the IP it uses
is not hard-coded in your torrc to be your former IP. Have you
configured your router NAT correctly?
Lastly, is it possible tha
Quoting Toralf Förster (2022-10-14 20:17:58)
> On 10/14/22 19:09, meskio wrote:
> > The upstream changelog is here:
> > https://gitlab.com/yawning/obfs4/-/blob/master/ChangeLog
> > But I understand is not easy to understand what the problem is from that
> > changelog.
>
> Indeed.
>
> BTW the fix
Quoting Toralf Förster (2022-10-16 11:23:18)
> On 10/16/22 09:50, Toralf Förster wrote:
> >
> > After configuring the installation of the unattended_upgrade package to
> > consider all packages [1] the new obfs4proxy was installed - but Tor was
> > not restarted nor obfs4proxy reloaded.
> >
> > Isn
On 10/17/22 11:41, meskio wrote:
Will be nice to add those fixes to the package. Maybe you can open two issues on
the debian bugtracker for them.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021911.
--
Toralf
___
tor-relays mailing list
tor-re
Quoting Toralf Förster (2022-10-17 12:56:04)
> On 10/17/22 11:41, meskio wrote:
> > Will be nice to add those fixes to the package. Maybe you can open two
> > issues on
> > the debian bugtracker for them.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021911.
Thank you :)
--
meskio | h
