[tor-relays] Confusing bridge signs...

[lists at for-privacy.net]

On Samstag, 18. Februar 2023 18:56:00 CET Keifer Bly wrote:
> Ok. Here is the torrc file:
> 
>   GNU nano 3.2                                   /etc/tor/torrc
> 
> 
> Nickname gbridge
> ORPort 443
> SocksPort 0
> BridgeRelay 1
> PublishServerDescriptor bridge
> ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
> ServerTransportListenAddr obfs4 0.0.0.0:8080
> ExtOrPort auto
> Log notice file /var/log/tor/notices.log
> ExitPolicy reject *:*
> AccountingMax 5 GB
> ContactInfo keiferdodderblyyatgmaildoddercom
> 
> 
> Where in this torrc file is that configured?
Then set it to 'any' and wait 24-48 hours to see what happens. Maybe there was 
an error in the db.

If your bridge is still not distributed, it could be due to the outdated 
obfs4proxy or because of 'AccountingMax 5 GB'.
Sorry but, 5 GB is a 'fart in the wind' the accounting period would only be a 
few hours a month. It's not even worth distributing them because it would only 
frustrate the users.

> And how would it be blocked in
> Russia already if it hasn't even been used?
Why should this new feature of the bridgedb, more precisely the rdsys backend, 
have anything to do with whether someone uses a bridge? This is a bridgedb 
distribution method introduced by meskio.


-- 
╰_╯ Ciao Marco!

Debian GNU/Linux

It's free software and it gives you freedom!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 3864 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20230220/27c8ec9e/attachment.sig>