Hi,
Weasel made some changes to how builds are made, so that the builds
are automatically retried for a few times when they fail for spurious
reasons.
Hopefully this should make the release process succeed more often.
Hi everyone,
If tor's geoip db (which indeed is IPFire) has the wrong country for
your IP, and you want it fixed, the correct place to fill an issue is
on IPFire's bugzilla.
You can see an instance of a previous report here
https://bugzilla.ipfire.org/show_bug.cgi?id=13037 .
It's not very
Hi,
this looks related to TROVE-2023-007 /
https://gitlab.torproject.org/tpo/core/tor/-/issues/40897 . It should
no longer appear after you upgrade.
If it still does, please do come back.
Regards,
trinity-1686a
On Mon, 18 Dec 2023 at 07:05, George Hartley via tor-relays
wrote:
>
> Hi,
>
>
Hi,
When using AccountingMax, tor tries to guess how long in will take for
it to use its quotas, and will decide deliberately to hibernate for
some time at the start of the period. It does that so not every relay
is working at its max capacity on the first of the month, and only the
unmetered
Hi,
For reasons not totally clear to me (something related to meek and
uTLS I think?) TorProject forked obfs4. To disambiguate with Yawning's
obfs4, the project was renamed to lyrebird.
It should work the same as obfs4.exe for your use case.
Would you mind creating a ticket in
Hi,
I get these warnings from time to time too. I believe they are rather
benign, though I wonder how a document with a 25:1 compression ratio
can happen in practice.
> Interestingly it's the dirport that
> ie requested. I thought the dirport is no longer in use - do the
> authorities still
Hi,
It [looks like `TestingSigningKeySlop`][1] might be what you are
looking for. I'm not entirely sure why it's categorized as a Testing
option, as it seems to do something useful outside of testing, so
maybe don't use it just yet?
There doesn't seem to be a way to print the expiration time from
> This has probably been addressed before but why isn't the MyFamily value just
> a single, unique ID?
There is a proposal to have some way of doing that in the future, but
that proposal isn't implemented
https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/proposals/321-happy-families.md
Hi,
I've heard once of a non-exit relay getting seized because it was used
as guard by a ransomware. We can't tell for sure, but maybe it's
something alike:
some kind of virus connecting to its control server over tor and
choosing this relay as its guard, causing your ip to be flagged by
some
culous when it comes to that, which is why it was set to
> so little. Ran killall -HUP tor to reload it and see that happens in the next
> day or so. And the reason why it's on port 443 is so as to be on a port
> that's not likely blocked by network administrators. Thank you.
> --
Hi,
Your torrc is correct wrt to distribution mechanism (your bridge is
indicating "bridge-distribution-request any" in the descriptor it
sends), but for the record, the line would have been
"BridgeDistribution any".
A bridge uses less bandwidth than a relay, but it's still a proxy. At
5GB per
Hi,
You shouldn't worry too much about your relay sometime appearing as
overloaded. Sadly due to the ongoing network ddos, many relays show up
that way. You shouldn't restart your relay daily, that would make everybody
think it's not very stable, so you won't be able to get flags such as Stable,
Hi,
Tortilla:
The keys being used on this signature are the keys of DGoulet and Ahf
(two members of the network team). You can find links to their keys on
this page https://www.torproject.org/about/people/ .
You can also read this thread on the forum:
Hi,
That IP address used to belong to Faravahar, which is in the progress
of being relocated and
hasn't found its new home yet
(https://gitlab.torproject.org/tpo/core/tor/-/issues/40688). You
can safely ignore this error.
If you want a more up to date list, you can check the IP shown on
Hi,
These lines Toralf references come from the logs you sent. It looks
like apparmor didn't want obfs4proxy to open some file.
I'm not sure why obfs4proxy would care about this file, maybe it's
something the go runtime likes to look at. It does not look fatal
though.
Logs also says
> Dec 20
Hi,
There is nothing to do for your relay to work as an HSDirectory.
DirAuths will vote for you being an HSDirectory if they think you
are stable enough (I can't recall the exact rules, something like good
average time between failure, and at least 4 days of uptime I think).
The config lines
Hi,
First thanks for operating a new relay and welcome
> The logs report success and the Relay Search shows my relay (Nickname:
> code9nRelay) running but the advertised bandwidth is 0 B/s.
> It’s been running for 13 hours or so and I see a new relay that has been
> running for 1 hour has an
Hi,
> I noticed that the obfs2, obfs3, and obfs4 transport names seem to be
> hardcoded into tor.
obfs2/3/4 has no special meaning to tor. In fact if you grep the
codebase, you'll find obfs2 and obfs4 appears only in comments and
tests, and obfs3 doesn't show up.
The ability of obfs4proxy to
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
Hi,
It looks like your storage might be full, and tor try to store something,
but can't due to lack of space. You should delete files you might no longer
require such as old logs or cache files (not necessarily from tor, but from
your system in general)
Le mar. 23 août 2022 à 08:30, toritdown
Hi,
There are two main mechanisms to limit relays bandwidth usage.
The first is by setting RelayBandwidthRate and RelayBandwidthBurst to limit
the average and peak bandwidth usage of your bridge.
The second is by setting AccountingMax, AccountingStart and possibly
accounting AccountingRule, to
Hi,
There are multiple bridges distributions mechanism. One is chosen at random
when your bridge first come to life, each being perfectly fine :
- moat: distributed automatically to Tor Browser users
- https: distributed on bridge-db website after solving a captcha
https://bridges.torproject.org/
does not contain `ORPort [::2]:9001` or something
similar.
Regards,
Trinity Pointard
Le mar. 20 oct. 2020 à 14:34, netaudit a écrit :
>
> Hi thank you for your reply
>
> As per your suggestion I checked it on the link you provided.
> I can see my exit relay here:
>
Hi,
Since a few days, my relay A8503903F97FF27F5D1C3CA38817329F581925E6
appear down according to metrics.torproject.org, and is not getting
the Running flag from 6 out of 9 authorities according to
consensus-health.torproject.org.
This happened when my ISP got an issue and my network falled back
24 matches
Mail list logo
