I think QUIC could be an improvement, though I'm worried adding QUIC
wouldn't remove the need for Tor over TLS, which might add more maintenance
burden.
Even with QUIC, we will need to support TLS for some time so as to not
partition the network. Also, it used to be that UDP was 2nd class citizen
Hi,
I'm highly suspicious of commit
3e18507dc75afcf0c6560e966c9f18942406b0c8 which adds a call to
geoip_note_client_seen with a NULL (==no PT) in
src/core/or/channeltls.c
It's fine for DoS defense, but it's likely what's messing up stats.
Regards,
trinity-1686a
On Tue, 3 Oct 2023 at 21:12, Davi
Hi,
Thanks for reporting this issue. It has already been reported and
fixed recently:
https://gitlab.torproject.org/tpo/core/tor/-/merge_requests/665
> Sorry, at the moment I've no clue what would be the correct way to send
> patches...
The correct way to send a patch is to open a merge request
Hi,
thanks for reporting this. I opened a issue on torsocks tracker with
the informations you provided:
https://gitlab.torproject.org/tpo/core/torsocks/-/issues/40014
Regards,
Trinity Pointard
On Sat, 17 Dec 2022 at 16:18, Florian Weimer wrote:
>
> This patch is needed to avoid an im
> Bridge URIs do not address the problem of multiple bridges in the same
QR. An
> idea could be to separate them by newlines.
QR-codes from BridgeDB are already big enough I can't scan them reliably on
my
phone. I think even if multiple bridges per QR-code is supported, BridgeDB
(and
anything al
